Systems and methods for a real-time synchronized electrical power system simulator for &#34;what-if&#34; analysis and prediction over electrical power networks

ABSTRACT

A system for real-time modeling of electrical system performance is disclosed. The system includes a data acquisition component, a power analytics server and a client terminal. The power analytics server is comprised of a virtual system modeling engine, an analytics engine and a power system simulation engine. The virtual system modeling engine is configured to generate predicted data output utilizing a first virtual system model. The analytics engine is configured to synchronize the first virtual system model when a difference between the real-time data output and the predicted data output exceeds a threshold. The power system simulation engine is configured to store and process patterns and facilitate modification of parameters on the first virtual system model to create a second virtual system model; and forecast an aspect of the electrical system operating under parameters of the second virtual system model. The client terminal displays the forecasted aspects.

APPLICATIONS FOR CLAIM OF PRIORITY

This application claims the benefit under 35 U.S.C. §119(e) of U.S.Provisional Application Ser. No. 60/862,703 filed Oct. 24, 2006. Thisapplication also claims priority as a Continuation-In-Part under 35U.S.C. §120 to U.S. patent application Ser. No. 11/775,146 filed Jul. 9,2007 and entitled “Systems and Methods for Real-Time Dynamic Simulationof Uninterruptible Power Supply Solutions and Their Control LogicSystems,” and in turn to U.S. Provisional Patent Application Ser. No.60/819,024 filed Jul. 7, 2006 and U.S. Provisional Application Ser. No.60/806,938 filed Jul. 11, 2006. The disclosures of the above-identifiedapplications are incorporated herein by reference as if set forth infull.

BACKGROUND

I. Field of the Invention

The present invention relates generally to computer modeling andmanagement of systems and, more particularly, to computer simulationtechniques with real-time system monitoring and optimization ofelectrical system performance.

II. Background of the Invention

Computer models of complex systems enable improved system design,development, and implementation through techniques for off-linesimulation of the system operation. That is, system models can becreated that computers can “operate” in a virtual environment todetermine design parameters. All manner of systems can be modeled,designed, and operated in this way, including machinery, factories,electrical power and distribution systems, processing plants, devices,chemical processes, biological systems, and the like. Such simulationtechniques have resulted in reduced development costs and superioroperation.

Design and production processes have benefited greatly from suchcomputer simulation techniques, and such techniques are relatively welldeveloped, but such techniques have not been applied in real-time, e.g.,for real-time operational monitoring and management. In addition,predictive failure analysis techniques do not generally use real-timedata that reflect actual system operation. Greater efforts at real-timeoperational monitoring and management would provide more accurate andtimely suggestions for operational decisions, and such techniquesapplied to failure analysis would provide improved predictions of systemproblems before they occur. With such improved techniques, operationalcosts could be greatly reduced.

For example, mission critical electrical systems, e.g., for data centersor nuclear power facilities, must be designed to ensure that power isalways available. Thus, the systems must be as failure proof aspossible, and many layers of redundancy must be designed in to ensurethat there is always a backup in case of a failure. It will beunderstood that such systems are highly complex, a complexity made evengreater as a result of the required redundancy. Computer design andmodeling programs allow for the design of such systems by allowing adesigner to model the system and simulate its operation. Thus, thedesigner can ensure that the system will operate as intended before thefacility is constructed.

Once the facility is constructed, however, the design is typically onlyreferred to when there is a failure. In other words, once there isfailure, the system design is used to trace the failure and takecorrective action; however, because such design are so complex, andthere are many interdependencies, it can be extremely difficult and timeconsuming to track the failure and all its dependencies and then takecorrective action that doesn't result in other system disturbances.

Moreover, changing or upgrading the system can similarly be timeconsuming and expensive, requiring an expert to model the potentialchange, e.g., using the design and modeling program. Unfortunately,system interdependencies can be difficult to simulate, making even minorchanges risky.

For example, no reliable means exists for simulating electrical systemperformance under various “what if” scenarios (i.e., the electricalsystem performing under different equipment configurations andoperational parameters). That is, there is currently no simulation or“blackboard” solution that exists for simulating real-time “what if”scenarios on an electrical power system for the purpose of analyzingtheir impact on the health, performance, and reliability of theelectrical system. This analysis is critical to the design of electricalsystems that can meet the power demands and maintain sufficient activeand reactive power reserves to handle the ongoing changes in demand anddisturbances to the system due to various contingencies.

Conventional systems use a rigid simulation model that does not take theactual power system alignment and aging effects into consideration whencomputing predicted electrical values. This makes it difficult if notimpossible to reliably simulate the performance characteristics of anelectrical system that is reflective of the real-time operationalconditions.

A virtual system model that can align itself in real-time with theactual electrical system configuration, and ages with the facility iscritical to obtaining predictions that are reflective of the ability ofthe electrical system to maintain operational reliability and stabilitywhen subjected to the “what if” scenarios under various contingencyconditions. Without real-time synchronization and an aging ability,predictions become of little value as they are no longer reflective ofthe actual facility status and may lead to false conclusions.

SUMMARY

Systems and methods for a real-time synchronized electrical power systemsimulator for “what-if” analysis and prediction over electrical powernetworks, are disclosed.

In one aspect, a system for real-time modeling of electrical systemperformance is disclosed. The system includes a data acquisitioncomponent, a power analytics server and a client terminal. The dataacquisition component is communicatively connected to a sensorconfigured to acquire real-time data output from the electrical system.The power analytics server is communicatively connected to the dataacquisition component and is comprised of a virtual system modelingengine, an analytics engine and a power system simulation engine.

The virtual system modeling engine is configured to generate predicteddata output for the electrical system utilizing a first virtual systemmodel of the electrical system. The analytics engine is configured tomonitor the real-time data output and the predicted data output of theelectrical system initiating a calibration and synchronization operationto update the first virtual system model when a difference between thereal-time data output and the predicted data output exceeds a threshold.The power system simulation engine is configured to store and processpatterns observed from the real-time data output and operate in ascenario builder mode to facilitate modification of parameters on thefirst virtual system model to create a second virtual system model; andforecast an aspect of the electrical system operating under the modifiedparameters of the second virtual system model.

The client terminal is communicatively connected to the power systemsimulation engine and configured to allow a system administrator tomodify the parameters of the first virtual system model when the powersystem simulation engine is operating in the scenario builder mode anddisplay a report of the forecasted aspects.

In another aspect, a method for real-time modeling of electrical systemperformance, is disclosed. A first virtual system model of theelectrical system is updated in response to real-time data. A parameterof the first virtual system is modified using a scenario builderapplication to create a second virtual system model. Electrical systemperformance is simulated using the second virtual system model. A reportis generated that forecasts an aspect of the electrical system.

These and other features, aspects, and embodiments of the invention aredescribed below in the section entitled “Detailed Description.”

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the principles disclosed herein,and the advantages thereof, reference is now made to the followingdescriptions taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is an illustration of a system for utilizing real-time data forpredictive analysis of the performance of a monitored system, inaccordance with one embodiment.

FIG. 2 is a diagram illustrating a detailed view of an analytics serverincluded in the system of FIG. 1.

FIG. 3 is a diagram illustrating how the system of FIG. 1 operates tosynchronize the operating parameters between a physical facility and avirtual system model of the facility.

FIG. 4 is an illustration of the scalability of a system for utilizingreal-time data for predictive analysis of the performance of a monitoredsystem, in accordance with one embodiment.

FIG. 5 is a block diagram that shows the configuration details of thesystem illustrated in FIG. 1, in accordance with one embodiment.

FIG. 6 is an illustration of a flowchart describing a method forreal-time monitoring and predictive analysis of a monitored system, inaccordance with one embodiment.

FIG. 7 is an illustration of a flowchart describing a method formanaging real-time updates to a virtual system model of a monitoredsystem, in accordance with one embodiment.

FIG. 8 is an illustration of a flowchart describing a method forsynchronizing real-time system data with a virtual system model of amonitored system, in accordance with one embodiment.

FIG. 9 is a flow chart illustrating an example method for updating thevirtual model in accordance with one embodiment.

FIG. 10 is a diagram illustrating an example process for monitoring thestatus of protective devices in a monitored system and updating avirtual model based on monitored data.

FIG. 11 is a flowchart illustrating an example process for determiningthe protective capabilities of the protective devices being monitored.

FIG. 12 is a diagram illustrating an example process for determining theprotective capabilities of a High Voltage Circuit Breaker (HVCB).

FIG. 13 is a flowchart illustrating an example process for determiningthe protective capabilities of the protective devices being monitored inaccordance with another embodiment.

FIG. 14 is a diagram illustrating a process for evaluating the withstandcapabilities of a MVCB in accordance with one embodiment

FIG. 15 is a flow chart illustrating an example process for analyzingthe reliability of an electrical power distribution and transmissionsystem in accordance with one embodiment.

FIG. 16 is a flow chart illustrating an example process for analyzingthe reliability of an electrical power distribution and transmissionsystem that takes weather information into account in accordance withone embodiment.

FIG. 17 is a diagram illustrating an example process for predicting inreal-time various parameters associated with an alternating current (AC)arc flash incident.

FIG. 18 is a flow chart illustrating an example process for real-timeanalysis of the operational stability of an electrical powerdistribution and transmission system in accordance with one embodiment.

FIG. 19 is a flow chart illustrating an example process for conducting areal-time power capacity assessment of an electrical power distributionand transmission system, in accordance with one embodiment.

FIG. 20 is a flow chart illustrating an example process for performingreal-time harmonics analysis of an electrical power distribution andtransmission system, in accordance with one embodiment.

FIG. 21 is a diagram illustrating how the HTM Pattern Recognition andMachine Learning Engine works in conjunction with the other elements ofthe analytics system to make predictions about the operational aspectsof a monitored system, in accordance with one embodiment.

FIG. 22 is an illustration of the various cognitive layers that comprisethe neocortical catalyst process used by the HTM Pattern Recognition andMachine Learning Engine to analyze and make predictions about theoperational aspects of a monitored system, in accordance with oneembodiment.

FIG. 23 is a flow chart illustrating an example process for real-timemodeling of an uninterruptible power supply (UPS) system protecting anelectrical power distribution and/or transmission system, in accordancewith one embodiment.

FIG. 24 is a diagram illustrating how the UPS Transient StabilitySimulation Engine works in conjunction with the other elements of theanalytics system to make predictions about the operational aspects ofthe UPS controls solution protecting the electrical system, inaccordance with one embodiment.

FIG. 25, is an illustration of the interactions between the UPSTransient Stability Simulation Engine and the UPS control logic model,in accordance with one embodiment.

FIG. 26, is a depiction of the various pre-defined UPS control blocks(functions) that can be used to create a user-defined UPS control logicmodel, in accordance with one embodiment.

FIG. 27 is an illustration that depicts the process of building a UPScontrol logic model, in accordance with one embodiment.

FIG. 28A is a sample illustration of a control block diagram for anexcitation system, in accordance with one embodiment.

FIG. 28B is a sample illustration of a control block diagram for aturbine system, in accordance with one embodiment.

FIG. 29 is an illustration of a closed loop AVR control logic modelbuilt with the pre-defined control logic blocks, in accordance with oneembodiment.

FIG. 30 is an illustration of the power path in a UPS system moduleduring a normal operation mode, in accordance with one embodiment.

FIG. 31 is an illustration of the power path in a UPS system moduleduring a bypass operation mode, in accordance with one embodiment.

FIG. 32 is an illustration of the power path in a UPS system moduleduring a battery power operation mode, in accordance with oneembodiment.

FIG. 33 is an illustration of a UPS control logic diagram thatdemonstrates how the UPS system functions when operating under a bypassoperation mode, in accordance with one embodiment.

FIG. 34 is a depiction of an input window with sample user-definedsystem conditions triggering the UPS controls solution to switch to abypass operation mode, in accordance with one embodiment.

FIG. 35 is a depiction of a UPS simulation results window showing thepower and current flows into the STS1 and STS2 breaker as the UPS systemswitches from a normal operation mode to a bypass operation mode, inaccordance with one embodiment.

FIG. 36 is a depiction of a UPS simulation results window showing thevoltage and frequency values in the load bus as the UPS system switchesfrom a normal operation mode to a bypass operation mode, in accordancewith one embodiment.

FIG. 37 is a diagram illustrating how the Power System Simulation Engineworks in conjunction with the other elements of the analytics system tomake “what-if” predictions about the health, performance and reliabilityof an electrical system, in accordance with one embodiment.

FIG. 38 is a conceptual depiction of the synchronization of the actualphysical world (right side) and virtual world (left side), in accordancewith one embodiment.

FIG. 39 is an illustration of how a blackboard scenario builder can beused modify various parameters of a virtual system model for simulatingthe impact of various “what-if” scenarios on the health, performance andreliability of an electrical system, in accordance with one embodiment.

FIG. 40 is a flowchart illustrating an example process for simulatinghow “what-if” scenarios impact the health, performance and reliabilityof an electrical system, in accordance with one embodiment.

FIG. 41 is a snapshot of a 2D and 3D visualization of the electricalsystem generated by a blackboard simulation, in accordance with oneembodiment.

DETAILED DESCRIPTION

Systems and methods for a real-time synchronized electrical power systemsimulator for “what-if” analysis and prediction over electrical powernetworks, are disclosed. It will be clear, however, that the presentinvention may be practiced without some or all of these specificdetails. In other instances, well known process operations have not beendescribed in detail in order not to unnecessarily obscure the presentinvention.

As used herein, a system denotes a set of components, real or abstract,comprising a whole where each component interacts with or is related toat least one other component within the whole. Examples of systemsinclude machinery, factories, electrical systems, processing plants,devices, chemical processes, biological systems, data centers, aircraftcarriers, and the like. An electrical system can designate a powergeneration and/or distribution system that is widely dispersed (i.e.,power generation, transformers, and/or electrical distributioncomponents distributed geographically throughout a large region) orbounded within a particular location (e.g., a power plant within aproduction facility, a bounded geographic area, on board a ship, etc.).

A network application is any application that is stored on anapplication server connected to a network (e.g., local area network,wide area network, etc.) in accordance with any contemporaryclient/server architecture model and can be accessed via the network. Inthis arrangement, the network application programming interface (API)resides on the application server separate from the client machine. Theclient interface would typically be a web browser (e.g. INTERNETEXPLORER™, FIREFOX™, NETSCAPE™, etc) that is in communication with thenetwork application server via a network connection (e.g., HTTP, HTTPS,RSS, etc.).

FIG. 1 is an illustration of a system for utilizing real-time data forpredictive analysis of the performance of a monitored system, inaccordance with one embodiment. As shown herein, the system 100 includesa series of sensors (i.e., Sensor A 104, Sensor B 106, Sensor C 108)interfaced with the various components of a monitored system 102, a dataacquisition hub 112, an analytics server 116, and a thin-client device128. In one embodiment, the monitored system 102 is an electrical powergeneration plant. In another embodiment, the monitored system 102 is anelectrical power transmission infrastructure. In still anotherembodiment, the monitored system 102 is an electrical power distributionsystem. In still another embodiment, the monitored system 102 includes acombination of one or more electrical power generation plant(s), powertransmission infrastructure(s), and/or an electrical power distributionsystem. It should be understood that the monitored system 102 can be anycombination of components whose operations can be monitored withconventional sensors and where each component interacts with or isrelated to at least one other component within the combination. For amonitored system 102 that is an electrical power generation,transmission, or distribution system, the sensors can provide data suchas voltage, frequency, current, power, power factor, and the like.

The sensors are configured to provide output values for systemparameters that indicate the operational status and/or “health” of themonitored system 102. For example, in an electrical power generationsystem, the current output or voltage readings for the variouscomponents that comprise the power generation system is indicative ofthe overall health and/or operational condition of the system. In oneembodiment, the sensors are configured to also measure additional datathat can affect system operation. For example, for an electrical powerdistribution system, the sensor output can include environmentalinformation, e.g., temperature, humidity, etc., which can impactelectrical power demand and can also affect the operation and efficiencyof the power distribution system itself.

Continuing with FIG. 1, in one embodiment, the sensors are configured tooutput data in an analog format. For example, electrical power sensormeasurements (e.g., voltage, current, etc.) are sometimes conveyed in ananalog format as the measurements may be continuous in both time andamplitude. In another embodiment, the sensors are configured to outputdata in a digital format. For example, the same electrical power sensormeasurements may be taken in discrete time increments that are notcontinuous in time or amplitude. In still another embodiment, thesensors are configured to output data in either an analog or digitalformat depending on the sampling requirements of the monitored system102.

The sensors can be configured to capture output data at split-secondintervals to effectuate “real time” data capture. For example, in oneembodiment, the sensors can be configured to generate hundreds ofthousands of data readings per second. It should be appreciated,however, that the number of data output readings taken by a sensor maybe set to any value as long as the operational limits of the sensor andthe data processing capabilities of the data acquisition hub 112 are notexceeded.

Still with FIG. 1, each sensor is communicatively connected to the dataacquisition hub 112 via an analog or digital data connection 110. Thedata acquisition hub 112 may be a standalone unit or integrated withinthe analytics server 116 and can be embodied as a piece of hardware,software, or some combination thereof. In one embodiment, the dataconnection 110 is a “hard wired” physical data connection (e.g., serial,network, etc.). For example, a serial or parallel cable connectionbetween the sensor and the hub 112. In another embodiment, the dataconnection 110 is a wireless data connection. For example, a radiofrequency (RF), BLUETOOTH™, infrared or equivalent connection betweenthe sensor and the hub 112.

The data acquisition hub 112 is configured to communicate “real-time”data from the monitored system 102 to the analytics server 116 using anetwork connection 114. In one embodiment, the network connection 114 isa “hardwired” physical connection. For example, the data acquisition hub112 may be communicatively connected (via Category 5 (CAT5), fiber opticor equivalent cabling) to a data server (not shown) that iscommunicatively connected (via CAT5, fiber optic or equivalent cabling)through the Internet and to the analytics server 116 server. Theanalytics server 116 being also communicatively connected with theInternet (via CAT5, fiber optic, or equivalent cabling). In anotherembodiment, the network connection 114 is a wireless network connection(e.g., Wi-Fi, WLAN, etc.). For example, utilizing an 802.11b/g orequivalent transmission format. In practice, the network connectionutilized is dependent upon the particular requirements of the monitoredsystem 102.

Data acquisition hub 112 can also be configured to supply warning andalarms signals as well as control signals to monitored system 102 and/orsensors 104, 106, and 108 as described in more detail below.

As shown in FIG. 1, in one embodiment, the analytics server 116 hosts ananalytics engine 118, virtual system modeling engine 124 and severaldatabases 126, 130, and 132. The virtual system modeling engine can,e.g., be a computer modeling system, such as described above. In thiscontext, however, the modeling engine can be used to precisely model andmirror the actual electrical system. Analytics engine 118 can beconfigured to generate predicted data for the monitored system andanalyze difference between the predicted data and the real-time datareceived from hub 112.

FIG. 2 is a diagram illustrating a more detailed view of analytic server116. As can be seen, analytic server 116 is interfaced with a monitoredfacility 102 via sensors 202, e.g., sensors 104, 106, and 108. Sensors202 are configured to supply real-time data from within monitoredfacility 102. The real-time data is communicated to analytic server 116via a hub 204. Hub 204 can be configure to provide real-time data toserver 116 as well as alarming, sensing and control featured forfacility 102.

The real-time data from hub 204 can be passed to a comparison engine210, which can form part of analytics engine 118. Comparison engine 210can be configured to continuously compare the real-time data withpredicted values generated by simulation engine 208. Based on thecomparison, comparison engine 210 can be further configured to determinewhether deviations between the real-time and the expected values exists,and if so to classify the deviation, e.g., high, marginal, low, etc. Thedeviation level can then be communicated to decision engine 212, whichcan also comprise part of analytics engine 118.

Decision engine 212 can be configured to look for significant deviationsbetween the predicted values and real-time values as received from thecomparison engine 210. If significant deviations are detected, decisionengine 212 can also be configured to determine whether an alarmcondition exists, activate the alarm and communicate the alarm toHuman-Machine Interface (HMI) 214 for display in real-time via, e.g.,thin client 128. Decision engine 212 can also be configured to performroot cause analysis for significant deviations in order to determine theinterdependencies and identify the parent-child failure relationshipsthat may be occurring. In this manner, parent alarm conditions are notdrowned out by multiple children alarm conditions, allowing theuser/operator to focus on the main problem, at least at first.

Thus, in one embodiment, and alarm condition for the parent can bedisplayed via HMI 214 along with an indication that processes andequipment dependent on the parent process or equipment are also in alarmcondition. This also means that server 116 can maintain a parent-childlogical relationship between processes and equipment comprising facility102. Further, the processes can be classified as critical, essential,non-essential, etc.

Decision engine 212 can also be configured to determine health andperformance levels and indicate these levels for the various processesand equipment via HMI 214. All of which, when combined with the analyticcapabilities of analytics engine 118 allows the operator to minimize therisk of catastrophic equipment failure by predicting future failures andproviding prompt, informative information concerning potential/predictedfailures before they occur. Avoiding catastrophic failures reduces riskand cost, and maximizes facility performance and up time.

Simulation engine 208 operates on complex logical models 206 of facility102. These models are continuously and automatically synchronized withthe actual facility status based on the real-time data provided by hub204. In other words, the models are updated based on current switchstatus, breaker status, e.g., open-closed, equipment on/off status, etc.Thus, the models are automatically updated based on such status, whichallows simulation engine to produce predicted data based on the currentfacility status. This in turn, allows accurate and meaningfulcomparisons of the real-time data to the predicted data.

Example models 206 that can be maintained and used by server 116 includepower flow models used to calculate expected kW, kVAR, power factorvalues, etc., short circuit models used to calculate maximum and minimumavailable fault currents, protection models used to determine properprotection schemes and ensure selective coordination of protectivedevices, power quality models used to determine voltage and currentdistortions at any point in the network, to name just a few. It will beunderstood that different models can be used depending on the systembeing modeled.

In certain embodiments, hub 204 is configured to supply equipmentidentification associated with the real-time data. This identificationcan be cross referenced with identifications provided in the models.

In one embodiment, if the comparison performed by comparison engine 210indicates that the differential between the real-time sensor outputvalue and the expected value exceeds a Defined Difference Tolerance(DDT) value (i.e., the “real-time” output values of the sensor output donot indicate an alarm condition) but below an alarm condition (i.e.,alarm threshold value), a calibration request is generated by theanalytics engine 118. If the differential exceeds, the alarm condition,an alarm or notification message is generated by the analytics engine118. If the differential is below the DTT value, the analytics enginedoes nothing and continues to monitor the real-time data and expecteddata.

In one embodiment, the alarm or notification message is sent directly tothe client (i.e., user) 128, e.g., via HMI 214, for display in real-timeon a web browser, pop-up message box, e-mail, or equivalent on theclient 128 display panel. In another embodiment, the alarm ornotification message is sent to a wireless mobile device (e.g.,BLACKBERRY™, laptop, pager, etc.) to be displayed for the user by way ofa wireless router or equivalent device interfaced with the analyticsserver 116. In still another embodiment, the alarm or notificationmessage is sent to both the client 128 display and the wireless mobiledevice. The alarm can be indicative of a need for a repair event ormaintenance to be done on the monitored system. It should be noted,however, that calibration requests should not be allowed if an alarmcondition exists to prevent the models form being calibrated to anabnormal state.

Once the calibration is generated by the analytics engine 118, thevarious operating parameters or conditions of model(s) 206 can beupdated or adjusted to reflect the actual facility configuration. Thiscan include, but is not limited to, modifying the predicted data outputfrom the simulation engine 208, adjusting the logic/processingparameters utilized by the model(s) 206, adding/subtracting functionalelements from model(s) 206, etc. It should be understood, that anyoperational parameter of models 206 can be modified as long as theresulting modifications can be processed and registered by simulationengine 208.

Referring back to FIG. 1, models 206 can be stored in the virtual systemmodel database 126. As noted, a variety of conventional virtual modelapplications can be used for creating a virtual system model, so that awide variety of systems and system parameters can be modeled. Forexample, in the context of an electrical power distribution system, thevirtual system model can include components for modeling reliability,voltage stability, and power flow. In addition, models 206 can includedynamic control logic that permits a user to configure the models 206 byspecifying control algorithms and logic blocks in addition tocombinations and interconnections of generators, governors, relays,breakers, transmission line, and the like. The voltage stabilityparameters can indicate capacity in terms of size, supply, anddistribution, and can indicate availability in terms of remainingcapacity of the presently configured system. The power flow model canspecify voltage, frequency, and power factor, thus representing the“health” of the system.

All of models 206 can be referred to as a virtual system model. Thus,virtual system model database can be configured to store the virtualsystem model. A duplicate, but synchronized copy of the virtual systemmodel can be stored in a virtual simulation model database 130. Thisduplicate model can be used for what-if simulations. In other words,this model can be used to allow a system designer to make hypotheticalchanges to the facility and test the resulting effect, without takingdown the facility or costly and time consuming analysis. Suchhypothetical can be used to learn failure patterns and signatures aswell as to test proposed modifications, upgrades, additions, etc., forthe facility. The real-time data, as well as trending produced byanalytics engine 118 can be stored in a real-time data acquisitiondatabase 132.

As discussed above, the virtual system model is periodically calibratedand synchronized with “real-time” sensor data outputs so that thevirtual system model provides data output values that are consistentwith the actual “real-time” values received from the sensor outputsignals. Unlike conventional systems that use virtual system modelsprimarily for system design and implementation purposes (i.e., offlinesimulation and facility planning), the virtual system models describedherein are updated and calibrated with the real-time system operationaldata to provide better predictive output values. A divergence betweenthe real-time sensor output values and the predicted output valuesgenerate either an alarm condition for the values in question and/or acalibration request that is sent to the calibration engine 134.

Continuing with FIG. 1, the analytics engine 118 can be configured toimplement pattern/sequence recognition into a real-time decision loopthat, e.g., is enabled by a new type of machine learning calledassociative memory, or hierarchical temporal memory (HTM), which is abiological approach to learning and pattern recognition. Associativememory allows storage, discovery, and retrieval of learned associationsbetween extremely large numbers of attributes in real time. At a basiclevel, an associative memory stores information about how attributes andtheir respective features occur together. The predictive power of theassociative memory technology comes from its ability to interpret andanalyze these co-occurrences and to produce various metrics. Associativememory is built through “experiential” learning in which each newlyobserved state is accumulated in the associative memory as a basis forinterpreting future events. Thus, by observing normal system operationover time, and the normal predicted system operation over time, theassociative memory is able to learn normal patterns as a basis foridentifying non-normal behavior and appropriate responses, and toassociate patterns with particular outcomes, contexts or responses. Theanalytics engine 118 is also better able to understand component meantime to failure rates through observation and system availabilitycharacteristics. This technology in combination with the virtual systemmodel can be characterized as a “neocortical” model of the system undermanagement

This approach also presents a novel way to digest and comprehend alarmsin a manageable and coherent way. The neocortical model could assist inuncovering the patterns and sequencing of alarms to help pinpoint thelocation of the (impending) failure, its context, and even the cause.Typically, responding to the alarms is done manually by experts who havegained familiarity with the system through years of experience. However,at times, the amount of information is so great that an individualcannot respond fast enough or does not have the necessary expertise. An“intelligent” system like the neocortical system that observes andrecommends possible responses could improve the alarm management processby either supporting the existing operator, or even managing the systemautonomously.

Current simulation approaches for maintaining transient stabilityinvolve traditional numerical techniques and typically do not test allpossible scenarios. The problem is further complicated as the numbers ofcomponents and pathways increase. Through the application of theneocortical model, by observing simulations of circuits, and bycomparing them to actual system responses, it may be possible to improvethe simulation process, thereby improving the overall design of futurecircuits.

The virtual system model database 126, as well as databases 130 and 132,can be configured to store one or more virtual system models, virtualsimulation models, and real-time data values, each customized to aparticular system being monitored by the analytics server 118. Thus, theanalytics server 118 can be utilized to monitor more than one system ata time. As depicted herein, the databases 126, 130, and 132 can behosted on the analytics server 116 and communicatively interfaced withthe analytics engine 118. In other embodiments, databases 126, 130, and132 can be hosted on a separate database server (not shown) that iscommunicatively connected to the analytics server 116 in a manner thatallows the virtual system modeling engine 124 and analytics engine 118to access the databases as needed.

Therefore, in one embodiment, the client 128 can modify the virtualsystem model stored on the virtual system model database 126 by using avirtual system model development interface using well-known modelingtools that are separate from the other network interfaces. For example,dedicated software applications that run in conjunction with the networkinterface to allow a client 128 to create or modify the virtual systemmodels.

The client 128 may utilize a variety of network interfaces (e.g., webbrowser, CITRIX™, WINDOWS TERMINAL SERVICES™, telnet, or otherequivalent thin-client terminal applications, etc.) to access,configure, and modify the sensors (e.g., configuration files, etc.),analytics engine 118 (e.g., configuration files, analytics logic, etc.),calibration parameters (e.g., configuration files, calibrationparameters, etc.), virtual system modeling engine 124 (e.g.,configuration files, simulation parameters, etc.) and virtual systemmodel of the system under management (e.g., virtual system modeloperating parameters and configuration files). Correspondingly, datafrom those various components of the monitored system 102 can bedisplayed on a client 128 display panel for viewing by a systemadministrator or equivalent.

As described above, server 116 is configured to synchronize the physicalworld with the virtual and report, e.g., via visual, real-time display,deviations between the two as well as system health, alarm conditions,predicted failures, etc. This is illustrated with the aid of FIG. 3, inwhich the synchronization of the physical world (left side) and virtualworld (right side) is illustrated. In the physical world, sensors 202produce real-time data 302 for the processes 312 and equipment 314 thatmake up facility 102. In the virtual world, simulations 304 of thevirtual system model 206 provide predicted values 306, which arecorrelated and synchronized with the real-time data 302. The real-timedata can then be compared to the predicted values so that differences308 can be detected. The significance of these differences can bedetermined to determine the health status 310 of the system. The healthstats can then be communicated to the processes 312 and equipment 314,e.g., via alarms and indicators, as well as to thin client 128, e.g.,via web pages 316.

FIG. 4 is an illustration of the scalability of a system for utilizingreal-time data for predictive analysis of the performance of a monitoredsystem, in accordance with one embodiment. As depicted herein, ananalytics central server 422 is communicatively connected with analyticsserver A 414, analytics server B 416, and analytics server n 418 (i.e.,one or more other analytics servers) by way of one or more networkconnections 114. Each of the analytics servers is communicativelyconnected with a respective data acquisition hub (i.e., Hub A 408, Hub B410, Hub n 412) that communicates with one or more sensors that areinterfaced with a system (i.e., Monitored System A 402, Monitored SystemB 404, Monitored System n 406) that the respective analytical servermonitors. For example, analytics server A 414 is communicative connectedwith data acquisition hub A 408, which communicates with one or moresensors interfaced with monitored system A 402.

Each analytics server (i.e., analytics server A 414, analytics server B416, analytics server n 418) is configured to monitor the sensor outputdata of its corresponding monitored system and feed that data to thecentral analytics server 422. Additionally, each of the analyticsservers can function as a proxy agent of the central analytics server422 during the modifying and/or adjusting of the operating parameters ofthe system sensors they monitor. For example, analytics server B 416 isconfigured to be utilized as a proxy to modify the operating parametersof the sensors interfaced with monitored system B 404.

Moreover, the central analytics server 422, which is communicativelyconnected to one or more analytics server(s) can be used to enhance thescalability. For example, a central analytics server 422 can be used tomonitor multiple electrical power generation facilities (i.e., monitoredsystem A 402 can be a power generation facility located in city A whilemonitored system B 404 is a power generation facility located in city B)on an electrical power grid. In this example, the number of electricalpower generation facilities that can be monitored by central analyticsserver 422 is limited only by the data processing capacity of thecentral analytics server 422. The central analytics server 422 can beconfigured to enable a client 128 to modify and adjust the operationalparameters of any the analytics servers communicatively connected to thecentral analytics server 422. Furthermore, as discussed above, each ofthe analytics servers are configured to serve as proxies for the centralanalytics server 422 to enable a client 128 to modify and/or adjust theoperating parameters of the sensors interfaced with the systems thatthey respectively monitor. For example, the client 128 can use thecentral analytics server 422, and vice versa, to modify and/or adjustthe operating parameters of analytics server A 414 and utilize the sameto modify and/or adjust the operating parameters of the sensorsinterfaced with monitored system A 402. Additionally, each of theanalytics servers can be configured to allow a client 128 to modify thevirtual system model through a virtual system model developmentinterface using well-known modeling tools.

In one embodiment, the central analytics server 422 can function tomonitor and control a monitored system when its corresponding analyticsserver is out of operation. For example, central analytics server 422can take over the functionality of analytics server B 416 when theserver 416 is out of operation. That is, the central analytics server422 can monitor the data output from monitored system B 404 and modifyand/or adjust the operating parameters of the sensors that areinterfaced with the system 404.

In one embodiment, the network connection 114 is established through awide area network (WAN) such as the Internet. In another embodiment, thenetwork connection is established through a local area network (LAN)such as the company intranet. In a separate embodiment, the networkconnection 114 is a “hardwired” physical connection. For example, thedata acquisition hub 112 may be communicatively connected (via Category5 (CAT5), fiber optic or equivalent cabling) to a data server that iscommunicatively connected (via CAT5, fiber optic or equivalent cabling)through the Internet and to the analytics server 116 server hosting theanalytics engine 118. In another embodiment, the network connection 114is a wireless network connection (e.g., Wi-Fi, WLAN, etc.). For example,utilizing an 802.11b/g or equivalent transmission format.

In certain embodiments, regional analytics servers can be placed betweenlocal analytics servers 414, 416, . . . , 418 and central analyticsserver 422. Further, in certain embodiments a disaster recovery site canbe included at the central analytics server 422 level.

FIG. 5 is a block diagram that shows the configuration details ofanalytics server 116 illustrated in FIG. 1 in more detail. It should beunderstood that the configuration details in FIG. 5 are merely oneembodiment of the items described for FIG. 1, and it should beunderstood that alternate configurations and arrangements of componentscould also provide the functionality described herein.

The analytics server 116 includes a variety of components. In the FIG. 5embodiment, the analytics server 116 is implemented in a Web-basedconfiguration, so that the analytics server 116 includes (orcommunicates with) a secure web server 530 for communication with thesensor systems 519 (e.g., data acquisition units, metering devices,sensors, etc.) and external communication entities 534 (e.g., webbrowser, “thin client” applications, etc.). A variety of user views andfunctions 532 are available to the client 128 such as: alarm reports,Active X controls, equipment views, view editor tool, custom userinterface page, and XML parser. It should be appreciated, however, thatthese are just examples of a few in a long list of views and functions532 that the analytics server 116 can deliver to the externalcommunications entities 534 and are not meant to limit the types ofviews and functions 532 available to the analytics server 116 in anyway.

The analytics server 116 also includes an alarm engine 506 and messagingengine 504, for the aforementioned external communications. The alarmengine 506 is configured to work in conjunction with the messagingengine 504 to generate alarm or notification messages 502 (in the formof text messages, e-mails, paging, etc.) in response to the alarmconditions previously described. The analytics server 116 determinesalarm conditions based on output data it receives from the varioussensor systems 519 through a communications connection (e.g., wireless516, TCP/IP 518, Serial 520, etc) and simulated output data from avirtual system model 512, of the monitored system, processed by theanalytics engines 118. In one embodiment, the virtual system model 512is created by a user through interacting with an external communicationentity 534 by specifying the components that comprise the monitoredsystem and by specifying relationships between the components of themonitored system. In another embodiment, the virtual system model 512 isautomatically generated by the analytics engines 118 as components ofthe monitored system are brought online and interfaced with theanalytics server 508.

Continuing with FIG. 5, a virtual system model database 526 iscommunicatively connected with the analytics server 116 and isconfigured to store one or more virtual system models 512, each of whichrepresents a particular monitored system. For example, the analyticsserver 116 can conceivably monitor multiple electrical power generationsystems (e.g., system A, system B, system C, etc.) spread across a widegeographic area (e.g., City A, City B, City C, etc.). Therefore, theanalytics server 116 will utilize a different virtual system model 512for each of the electrical power generation systems that it monitors.Virtual simulation model database 538 can be configured to store asynchronized, duplicate copy of the virtual system model 512, andreal-time data acquisition database 540 can store the real-time andtrending data for the system(s) being monitored.

Thus, in operation, analytics server 116 can receive real-time data forvarious sensors, i.e., components, through data acquisition system 202.As can be seen, analytics server 116 can comprise various driversconfigured to interface with the various types of sensors, etc.,comprising data acquisition system 202. This data represents thereal-time operational data for the various components. For example, thedata may indicate that a certain component is operating at a certainvoltage level and drawing certain amount of current. This informationcan then be fed to a modeling engine to generate a virtual system model612 that is based on the actual real-time operational data.

Analytics engine 118 can be configured to compare predicted data basedon the virtual system model 512 with real-time data received from dataacquisition system 202 and to identify any differences. In someinstances, analytics engine can be configured to identify thesedifferences and then update, i.e., calibrate, the virtual system model512 for use in future comparisons. In this manner, more accuratecomparisons and warnings can be generated.

But in other instances, the differences will indicate a failure, or thepotential for a failure. For example, when a component begins to fail,the operating parameters will begin to change. This change may be suddenor it may be a progressive change over time. Analytics engine 118 candetect such changes and issue warnings that can allow the changes to bedetected before a failure occurs. The analytic engine 118 can beconfigured to generate warnings that can be communicated via interface532.

For example, a user can access information from server 116 using thinclient 534. For example, reports can be generate and served to thinclient 534 via server 540. These reports can, for example, compriseschematic or symbolic illustrations of the system being monitored.Status information for each component can be illustrated or communicatedfor each component. This information can be numerical, i.e., the voltageor current level. Or it can be symbolic, i.e., green for normal, red forfailure or warning. In certain embodiments, intermediate levels offailure can also be communicated, i.e., yellow can be used to indicateoperational conditions that project the potential for future failure. Itshould be noted that this information can be accessed in real-time.Moreover, via thin client 534, the information can be accessed formanywhere and anytime.

Continuing with FIG. 5, the Analytics Engine 118 is communicativelyinterfaced with a HTM Pattern Recognition and Machine Learning Engine551. The HTM Engine 551 is configured to work in conjunction with theAnalytics Engine 118 and a virtual system model of the monitored systemto make real-time predictions (i.e., forecasts) about variousoperational aspects of the monitored system. The HTM Engine 551 works byprocessing and storing patterns observed during the normal operation ofthe monitored system over time. These observations are provided in theform of real-time data captured using a multitude of sensors that areimbedded within the monitored system. In one embodiment, the virtualsystem model is also updated with the real-time data such that thevirtual system model “ages” along with the monitored system. Examples ofa monitored system includes machinery, factories, electrical systems,processing plants, devices, chemical processes, biological systems, datacenters, aircraft carriers, and the like. It should be understood thatthe monitored system can be any combination of components whoseoperations can be monitored with conventional sensors and where eachcomponent interacts with or is related to at least one other componentwithin the combination.

FIG. 6 is an illustration of a flowchart describing a method forreal-time monitoring and predictive analysis of a monitored system, inaccordance with one embodiment. Method 600 begins with operation 602where real-time data indicative of the monitored system status isprocessed to enable a virtual model of the monitored system undermanagement to be calibrated and synchronized with the real-time data. Inone embodiment, the monitored system 102 is a mission criticalelectrical power system. In another embodiment, the monitored system 102can include an electrical power transmission infrastructure. In stillanother embodiment, the monitored system 102 includes a combination ofthereof. It should be understood that the monitored system 102 can beany combination of components whose operations can be monitored withconventional sensors and where each component interacts with or isrelated to at least one other component within the combination.

Method 600 moves on to operation 604 where the virtual system model ofthe monitored system under management is updated in response to thereal-time data. This may include, but is not limited to, modifying thesimulated data output from the virtual system model, adjusting thelogic/processing parameters utilized by the virtual system modelingengine to simulate the operation of the monitored system,adding/subtracting functional elements of the virtual system model, etc.It should be understood, that any operational parameter of the virtualsystem modeling engine and/or the virtual system model may be modifiedby the calibration engine as long as the resulting modifications can beprocessed and registered by the virtual system modeling engine.

Method 600 proceeds on to operation 606 where the simulated real-timedata indicative of the monitored system status is compared with acorresponding virtual system model created at the design stage. Thedesign stage models, which may be calibrated and updated based onreal-time monitored data, are used as a basis for the predictedperformance of the system. The real-time monitored data can then providethe actual performance over time. By comparing the real-time time datawith the predicted performance information, difference can be identifieda tracked by, e.g., the analytics engine 118. Analytics engines 118 canthen track trends, determine alarm states, etc., and generate areal-time report of the system status in response to the comparison.

In other words, the analytics can be used to analyze the comparison andreal-time data and determine if there is a problem that should bereported and what level the problem may be, e.g., low priority, highpriority, critical, etc. The analytics can also be used to predictfuture failures and time to failure, etc. In one embodiment, reports canbe displayed on a conventional web browser (e.g. INTERNET EXPLORER™,FIREFOX™, NETSCAPE™, etc) that is rendered on a standard personalcomputing (PC) device. In another embodiment, the “real-time” report canbe rendered on a “thin-client” computing device (e.g., CITRIX™, WINDOWSTERMINAL SERVICES™, telnet, or other equivalent thin-client terminalapplication). In still another embodiment, the report can be displayedon a wireless mobile device (e.g., BLACKBERRY™, laptop, pager, etc.).For example, in one embodiment, the “real-time” report can include suchinformation as the differential in a particular power parameter (i.e.,current, voltage, etc.) between the real-time measurements and thevirtual output data.

FIG. 7 is an illustration of a flowchart describing a method formanaging real-time updates to a virtual system model of a monitoredsystem, in accordance with one embodiment. Method 700 begins withoperation 702 where real-time data output from a sensor interfaced withthe monitored system is received. The sensor is configured to captureoutput data at split-second intervals to effectuate “real time” datacapture. For example, in one embodiment, the sensor is configured togenerate hundreds of thousands of data readings per second. It should beappreciated, however, that the number of data output readings taken bythe sensor may be set to any value as long as the operational limits ofthe sensor and the data processing capabilities of the data acquisitionhub are not exceeded.

Method 700 moves to operation 704 where the real-time data is processedinto a defined format. This would be a format that can be utilized bythe analytics server to analyze or compare the data with the simulateddata output from the virtual system model. In one embodiment, the datais converted from an analog signal to a digital signal. In anotherembodiment, the data is converted from a digital signal to an analogsignal. It should be understood, however, that the real-time data may beprocessed into any defined format as long as the analytics engine canutilize the resulting data in a comparison with simulated output datafrom a virtual system model of the monitored system.

Method 700 continues on to operation 706 where the predicted (i.e.,simulated) data for the monitored system is generated using a virtualsystem model of the monitored system. As discussed above, a virtualsystem modeling engine utilizes dynamic control logic stored in thevirtual system model to generate the predicted output data. Thepredicted data is supposed to be representative of data that shouldactually be generated and output from the monitored system.

Method 700 proceeds to operation 708 where a determination is made as towhether the difference between the real-time data output and thepredicted system data falls between a set value and an alarm conditionvalue, where if the difference falls between the set value and the alarmcondition value a virtual system model calibration and a response can begenerated. That is, if the comparison indicates that the differentialbetween the “real-time” sensor output value and the corresponding“virtual” model data output value exceeds a Defined Difference Tolerance(DDT) value (i.e., the “real-time” output values of the sensor output donot indicate an alarm condition) but below an alarm condition (i.e.,alarm threshold value), a response can be generated by the analyticsengine. In one embodiment, if the differential exceeds, the alarmcondition, an alarm or notification message is generated by theanalytics engine 118. In another embodiment, if the differential isbelow the DTT value, the analytics engine does nothing and continues tomonitor the “real-time” data and “virtual” data. Generally speaking, thecomparison of the set value and alarm condition is indicative of thefunctionality of one or more components of the monitored system.

FIG. 8 is an illustration of a flowchart describing a method forsynchronizing real-time system data with a virtual system model of amonitored system, in accordance with one embodiment. Method 800 beginswith operation 802 where a virtual system model calibration request isreceived. A virtual model calibration request can be generated by ananalytics engine whenever the difference between the real-time dataoutput and the predicted system data falls between a set value and analarm condition value.

Method 800 proceeds to operation 804 where the predicted system outputvalue for the virtual system model is updated with a real-time outputvalue for the monitored system. For example, if sensors interfaced withthe monitored system outputs a real-time current value of A, then thepredicted system output value for the virtual system model is adjustedto reflect a predicted current value of A.

Method 800 moves on to operation 806 where a difference between thereal-time sensor value measurement from a sensor integrated with themonitored system and a predicted sensor value for the sensor isdetermined. As discussed above, the analytics engine is configured toreceive “real-time” data from sensors interfaced with the monitoredsystem via the data acquisition hub (or, alternatively directly from thesensors) and “virtual” data from the virtual system modeling enginesimulating the data output from a virtual system model of the monitoredsystem. In one embodiment, the values are in units of electrical poweroutput (i.e., current or voltage) from an electrical power generation ortransmission system. It should be appreciated, however, that the valuescan essentially be any unit type as long as the sensors can beconfigured to output data in those units or the analytics engine canconvert the output data received from the sensors into the desired unittype before performing the comparison.

Method 800 continues on to operation 808 where the operating parametersof the virtual system model are adjusted to minimize the difference.This means that the logic parameters of the virtual system model that avirtual system modeling engine uses to simulate the data output fromactual sensors interfaced with the monitored system are adjusted so thatthe difference between the real-time data output and the simulated dataoutput is minimized. Correspondingly, this operation will update andadjust any virtual system model output parameters that are functions ofthe virtual system model sensor values. For example, in a powerdistribution environment, output parameters of power load or demandfactor might be a function of multiple sensor data values. The operatingparameters of the virtual system model that mimic the operation of thesensor will be adjusted to reflect the real-time data received fromthose sensors. In one embodiment, authorization from a systemadministrator is requested prior to the operating parameters of thevirtual system model being adjusted. This is to ensure that the systemadministrator is aware of the changes that are being made to the virtualsystem model. In one embodiment, after the completion of all the variouscalibration operations, a report is generated to provide a summary ofall the adjustments that have been made to the virtual system model.

As described above, virtual system modeling engine 124 can be configuredto model various aspects of the system to produce predicted values forthe operation of various components within monitored system 102. Thesepredicted values can be compared to actual values being received viadata acquisition hub 112. If the differences are greater than a certainthreshold, e.g., the DTT, but not in an alarm condition, then acalibration instruction can be generated. The calibration instructioncan cause a calibration engine 134 to update the virtual model beingused by system modeling engine 124 to reflect the new operatinginformation.

It will be understood that as monitored system 102 ages, or morespecifically the components comprising monitored system 102 age, thenthe operating parameters, e.g., currents and voltages associated withthose components will also change. Thus, the process of calibrating thevirtual model based on the actual operating information provides amechanism by which the virtual model can be aged along with themonitored system 102 so that the comparisons being generated byanalytics engine 118 are more meaningful.

At a high level, this process can be illustrated with the aid of FIG. 9,which is a flow chart illustrating an example method for updating thevirtual model in accordance with one embodiment. In step 902, data iscollected from, e.g., sensors 104, 106, and 108. For example, thesensors can be configured to monitor protective devices within anelectrical distribution system to determine and monitor the ability ofthe protective devices to withstand faults, which is describe in moredetail below.

In step 904, the data from the various sensors can be processed byanalytics engine 118 in order to evaluate various parameters related tomonitored system 102. In step 905, simulation engine 124 can beconfigured to generate predicted values for monitored system 102 using avirtual model of the system that can be compared to the parametersgenerated by analytics engine 118 in step 904. If there are differencesbetween the actual values and the predicted values, then the virtualmodel can be updated to ensure that the virtual model ages with theactual system 102.

It should be noted that as the monitored system 102 ages, variouscomponents can be repaired, replaced, or upgraded, which can also createdifferences between the simulated and actual data that is not an alarmcondition. Such activity can also lead to calibrations of the virtualmodel to ensure that the virtual model produces relevant predictedvalues. Thus, not only can the virtual model be updated to reflect agingof monitored system 102, but it can also be updated to reflectretrofits, repairs, etc.

As noted above, in certain embodiments, a logical model of a facilitieselectrical system, a data acquisition system (data acquisition hub 112),and power system simulation engines (modeling engine 124) can beintegrated with a logic and methods based approach to the adjustment ofkey database parameters within a virtual model of the electrical systemto evaluate the ability of protective devices within the electricaldistribution system to withstand faults and also effectively “age” thevirtual system with the actual system.

Only through such a process can predictions on the withstand abilitiesof protective devices, and the status, security and health of anelectrical system be accurately calculated. Accuracy is important as thepredictions can be used to arrive at actionable, mission critical orbusiness critical conclusions that may lead to the re-alignment of theelectrical distribution system for optimized performance or security.

FIGS. 10-12 are flow charts presenting logical flows for determining theability of protective devices within an electrical distribution systemto withstand faults and also effectively “age” the virtual system withthe actual system in accordance with one embodiment. FIG. 10 is adiagram illustrating an example process for monitoring the status ofprotective devices in a monitored system 102 and updating a virtualmodel based on monitored data. First, in step 1002, the status of theprotective devices can be monitored in real time. As mentioned,protective devices can include fuses, switches, relays, and circuitbreakers. Accordingly, the status of the fuses/switches, relays, and/orcircuit breakers, e.g., the open/close status, source and load status,and on or off status, can be monitored in step 1002. It can bedetermined, in step 1004, if there is any change in the status of themonitored devices. If there is a change, then in step 1006, the virtualmodel can be updated to reflect the status change, i.e., thecorresponding virtual components data can be updated to reflect theactual status of the various protective devices.

In step 1008, predicted values for the various components of monitoredsystem 102 can be generated. But it should be noted that these valuesare based on the current, real-time status of the monitored system. Instep 1010, it can be determined which predicted voltages are for avalue, such as a value for a node or load, which can be calibrated. Atthe same time, real time sensor data can be received in step 1012. Thisreal time data can be used to monitor the status in step 1002 and it canalso be compared with the predicted values in step 1014. As noted above,the difference between the predicted values and the real time data canalso be determined in step 1014.

Accordingly, meaningful predicted values based on the actual conditionof monitored system 102 can be generated in steps 1004 to 1010. Thesepredicted values can then be used to determine if further action shouldbe taken based on the comparison of step 1014. For example, if it isdetermined in step 1016 that the difference between the predicted valuesand the real time sensor data is less than or equal to a certainthreshold, e.g., DTT, then no action can be taken e.g., an instructionnot to perform calibration can be issued in step 1018. Alternatively, ifit is determined in step 1020 that the real time data is actuallyindicative of an alarm situation, e.g., is above an alarm threshold,then a do not calibrate instruction can be generated in step 1018 and analarm can be generated as described above. If the real time sensor datais not indicative of an alarm condition, and the difference between thereal time sensor data and the predicted values is greater than thethreshold, as determined in step 1022, then an initiate calibrationcommand can be generated in step 1024.

If an initiate calibration command is issued in step 1024, then afunction call to calibration engine 134 can be generated in step 1026.The function call will cause calibration engine 134 to update thevirtual model in step 1028 based on the real time sensor data. Acomparison between the real time data and predicted data can then begenerated in step 1030 and the differences between the two computed. Instep 1032, a user can be prompted as to whether or not the virtual modelshould in fact be updated. In other embodiments, the update can beautomatic, and step 1032 can be skipped. In step 1034, the virtual modelcould be updated. For example, the virtual model loads, buses, demandfactor, and/or percent running information can be updated based on theinformation obtained in step 1030. An initiate simulation instructioncan then be generated in step 1036, which can cause new predicted valuesto be generated based on the update of virtual model.

In this manner, the predicted values generated in step 1008 are not onlyupdated to reflect the actual operational status of monitored system102, but they are also updated to reflect natural changes in monitoredsystem 102 such as aging. Accordingly, realistic predicted values can begenerated in step 1008.

FIG. 11 is a flowchart illustrating an example process for determiningthe protective capabilities of the protective devices being monitored instep 1002. Depending on the embodiment, the protective devices can beevaluated in terms of the International Electrotechnical Commission(IEC) standards or in accordance with the United States or AmericanNational Standards Institute (ANSI) standards. It will be understood,that the process described in relation to FIG. 11 is not dependent on aparticular standard being used.

First, in step 1102, a short circuit analysis can be performed for theprotective device. Again, the protective device can be any one of avariety of protective device types. For example, the protective devicecan be a fuse or a switch, or some type of circuit breaker. It will beunderstood that there are various types of circuit breakers includingLow Voltage Circuit Breakers (LVCBs), High Voltage Circuit Breakers(HVCBs), Mid Voltage Circuit Breakers (MVCBs), Miniature CircuitBreakers (MCBs), Molded Case Circuit Breakers (MCCBs), Vacuum CircuitBreakers, and Air Circuit Breakers, to name just a few. Any one of thesevarious types of protective devices can be monitored and evaluated usingthe processes illustrated with respect to FIGS. 10-12.

For example, for LVCBs, or MCCBs, the short circuit current, symmetric(I_(sym)) or asymmetric (I_(asym)), and/or the peak current (I_(peak))can be determined in step 1102. For, e.g., LVCBs that are notinstantaneous trip circuit breakers, the short circuit current at adelayed time (I_(symdelay)) can be determined. For HVCBs, a first cycleshort circuit current (I_(sym)) and/or I_(peak) can be determined instep 1102. For fuses or switches, the short circuit current, symmetricor asymmetric, can be determined in step 1102. And for MVCBs the shortcircuit current interrupting time can be calculated. These are just someexamples of the types of short circuit analysis that can be performed inStep 1102 depending on the type of protective device being analyzed.

Once the short circuit analysis is performed in step 1102, various stepscan be carried out in order to determine the bracing capability of theprotective device. For example, if the protective device is a fuse orswitch, then the steps on the left hand side of FIG. 11 can be carriedout. In this case, the fuse rating can first be determined in step 1104.In this case, the fuse rating can be the current rating for the fuse.For certain fuses, the X/R can be calculated in step 1105 and theasymmetric short circuit current (I_(asym)) for the fuse can bedetermined in step 1106 using equation 1.I _(ASYM) =I _(SYM) √{square root over (1+2e ^(−2p/(X/R)))}  Eq 1

In other implementations, the inductants/reactants (X/R) ratio can becalculated instep 1108 and compared to a fuse test X/R to determine ifthe calculated X/R is greater than the fuse test X/R. The calculated X/Rcan be determined using the predicted values provided in step 1008.Various standard tests X/R values can be used for the fuse test X/Rvalues in step 1108. For example, standard test X/R values for a LVCBcan be as follows:

-   -   PCB, ICCB=6.59    -   MCCB, ICCB rated<=10,000 A=1.73    -   MCCB, ICCB rated 10,001-20,000A=3.18    -   MCCB, ICCB rated>20,000 A=4.9

If the calculated X/R is greater than the fuse test X/R, then in step1112, equation 12 can be used to calculate an adjusted symmetrical shortcircuit current (I_(adjsym)). $\begin{matrix}{I_{ADJSYM} = {I_{SYM}\left\{ \frac{\sqrt{1 + {2\quad{\mathbb{e}}^{{- 2}{p/{({{CALC}\quad{X/R}})}}}}}}{\sqrt{1 + {2{\mathbb{e}}^{{- 2}{p/{({{TEST}\quad{X/R}})}}}}}} \right\}}} & {{Eq}\quad 12}\end{matrix}$

If the calculated X/R is not greater than the fuse test X/R then Iadjsymcan be set equal to I_(sym) in step 1110. In step 1114, it can then bedetermined if the fuse rating (step 1104) is greater than or equal toI_(adjsym) or I_(asym). If it is, then it can determine in step 1118that the protected device has passed and the percent rating can becalculated in step 1120 as follows:${\%\quad{rating}} = \frac{I_{ADJSYM}}{{Device}\quad{rating}}$ or${\%\quad{rating}} = \frac{I_{ASYM}}{{Device}\quad{rating}}$

If it is determined in step 1114 that the device rating is not greaterthan or equal to I_(adjsym), then it can be determined that the deviceas failed in step 1116. The percent rating can still be calculating instep 1120.

For LVCBs, it can first be determined whether they are fused in step1122. If it is determined that the LVCB is not fused, then in step 1124can be determined if the LVCB is an instantaneous trip LVCB. If it isdetermined that the LVCB is an instantaneous trip LVCB, then in step1130 the first cycle fault X/R can be calculated and compared to acircuit breaker test X/R (see example values above) to determine if thefault X/R is greater than the circuit breaker test X/R. If the fault X/Ris not greater than the circuit breaker test X/R, then in step 1132 itcan be determined if the LVCB is peak rated. If it is peak rated, thenI_(peak) can be used in step 1146 below. If it is determined that theLVCB is not peak rated in step 1132, then I_(adjsym) can be set equal toI_(sym) in step 1140. In step 1146, it can be determined if the devicerating is greater or equal to I_(adjsym), or to I_(peak) as appropriate,for the LVCB.

If it is determined that the device rating is greater than or equal toI_(adjsym), then it can be determined that the LVCB has passed in step1148. The percent rating can then be determined using the equations forI_(adjsym) defined above (step 1120) in step 1152. If it is determinedthat the device rating is not greater than or equal to I_(adjsym), thenit can be determined that the device has failed in step 1150. Thepercent rating can still be calculated in step 1152.

If the calculated fault X/R is greater than the circuit breaker test X/Ras determined in step 1130, then it can be determined if the LVCB ispeak rated in step 1134. If the LVCB is not peak rated, then theI_(adjsym) can be determined using equation 12. If the LVCB is peakrated, then I_(peak) can be determined using equation 11.I _(PEAK)=√{square root over (2)}I _(SYM){1.02+0.98e ^(−3/(X/R))}  Eq 11

It can then be determined if the device rating is greater than or equalto I_(adjsym) or I_(peak) as appropriate. The pass/fail determinationscan then be made in steps 1148 and 1150 respectively, and the percentrating can be calculated in step 1152.${\%\quad{rating}} = \frac{I_{ADJSYM}}{{Device}\quad{rating}}$ or${\%\quad{rating}} = \frac{I_{PEAK}}{{Device}\quad{rating}}$

If the LVCB is not an instantaneous trip LVCB as determined in step1124, then a time delay calculation can be performed at step 1128followed by calculation of the fault X/R and a determination of whetherthe fault X/R is greater than the circuit breaker test X/R. If it isnot, then Iadjsym can be set equal to Isym in step 1136. If thecalculated fault at X/R is greater than the circuit breaker test X/R,then Iadjsymdelay can be calculated in step 1138 using the followingequation with, e.g., a 0.5 second maximum delay: $\begin{matrix}{I_{\underset{DELAY}{ADJSYM}} = {I_{\underset{DELAY}{SYM}}\left\{ \frac{\sqrt{1 + {2\quad{\mathbb{e}}^{{- 60}{p/{({{CALC}\quad{X/R}})}}}}}}{\sqrt{1 + {2\quad{\mathbb{e}}^{{- 60}\quad{p/{({{TEST}\quad{X/R}})}}}}}} \right\}}} & {{Eq}\quad 14}\end{matrix}$

It can then be determined if the device rating is greater than or equalto I_(adjsym) or I_(adjsymdelay). The pass/fail determinations can thenbe made in steps 1148 and 1150, respectively and the percent rating canbe calculated in step 1152.

If it is determined that the LVCB is fused in step 1122, then the faultX/R can be calculated in step 1126 and compared to the circuit breakertest X/R in order to determine if the calculated fault X/R is greaterthan the circuit breaker test X/R. If it is greater, then I_(adjsym) canbe calculated in step 1154 using the following equation: $\begin{matrix}{I_{ADJSYM} = {I_{SYM}\left\{ \frac{1.02 + {0.98\quad{\mathbb{e}}^{{- 3}/{({{CALC}\quad{X/R}})}}}}{1.02 + {0.98{\mathbb{e}}^{{- 3}/{({{TEST}\quad{X/R}})}}}} \right\}}} & {{Eq}\quad 13}\end{matrix}$

If the calculated fault X/R is not greater than the circuit breaker testX/R, then I_(adjsym) can be set equal to I_(sym) in step 1156. It canthen be determined if the device rating is greater than or equal toI_(adjsym) in step 1146. The pass/fail determinations can then becarried out in steps 1148 and 1150 respectively, and the percent ratingcan be determined in step 1152.

FIG. 12 is a diagram illustrating an example process for determining theprotective capabilities of a HVCB. In certain embodiments, X/R can becalculated in step 1157 and a peak current (I_(peak)) can be determinedusing equation 11 in step 1158. In step 1162, it can be determinedwhether the HVCB's rating is greater than or equal to I_(peak) asdetermined in step 1158. If the device rating is greater than or equalto I_(peak), then the device has passed in step 1164. Otherwise, thedevice fails in step 1166. In either case, the percent rating can bedetermined in step 1168 using the following:${\%\quad{rating}} = \frac{I_{PEAK}}{{Device}\quad{rating}}$

In other embodiments, an interrupting time calculation can be made instep 1170. In such embodiments, a fault X/R can be calculated and thencan be determined if the fault X/R is greater than or equal to a circuitbreaker test X/R in step 1172. For example, the following circuitbreaker test X/R can be used;

-   -   50 HzTestX/R=13.7    -   60 Hz Test X/R=16.7    -   (DC Time Contant=0.45 ms)

If the fault X/R is not greater than the circuit breaker test X/R thenI_(adjintsym) can be set equal to I_(sym) in step 1174. If thecalculated fault X/R is greater than the circuit breaker test X/R, thencontact parting time for the circuit breaker can be determined in step1176 and equation 15 can then be used to determine I_(adjintsym) in step1178. $\begin{matrix}{I_{\underset{SYM}{ADJINT}} = {I_{\underset{SYM}{INT}}\left\{ \frac{\sqrt{1 + {2{\mathbb{e}}^{{- 4}{pf}*{t/{({{CALCX}/R})}}}}}}{\sqrt{1 + {2{\mathbb{e}}^{{- 4}\quad{pf}*{t/{({{TEST}\quad{X/R}})}}}}}} \right\}}} & {{Eq}\quad 15}\end{matrix}$

In step 1180, it can be determined whether the device rating is greaterthan or equal to I_(adjintsym). The pass/fail determinations can then bemade in steps 1182 and 1184 respectively and the percent rating can becalculated in step 1186 using the following:${\%\quad{rating}} = \frac{I_{ADJINTSYM}}{{Device}\quad{rating}}$

FIG. 13 is a flowchart illustrating an example process for determiningthe protective capabilities of the protective devices being monitored instep 1002 in accordance with another embodiment. The process can startwith a short circuit analysis in step 1302. For systems operating at afrequency other than 60 hz, the protective device X/R can be modified asfollows:(X/R)mod=(X/R)*60 H/(system Hz).

For fuses/switches, a selection can be made, as appropriate, between useof the symmetrical rating or asymmetrical rating for the device. TheMultiplying Factor (MF) for the device can then be calculated in step1304. The MF can then be used to determine I_(adjasym) or I_(adjsym). Instep 1306, it can be determined if the device rating is greater than orequal to I_(adjasym) or I_(adjsym). Based on this determination, it canbe determined whether the device passed or failed in steps 1308 and 1310respectively, and the percent rating can be determined in step 1312using the following:% rating=I _(adjasym)*100/device rating; or% rating=I _(adjsym)*100/device rating.

For LVCBs, it can first be determined whether the device is fused instep 1314. If the device is not fused, then in step 1315 it can bedetermined whether the X/R is known for the device. If it is known, thenthe LVF can be calculated for the device in step 1320. It should benoted that the LVF can vary depending on whether the LVCB is aninstantaneous trip device or not. If the X/R is not known, then it canbe determined in step 1317, e.g., using the following:

-   -   PCB, ICCB=6.59    -   MCCB, ICCB rated<=10,000 A=1.73    -   MCCB, ICCB rated 10,001-20,000A=3.18    -   MCCB, ICCB rated>20,000 A=4.9

If the device is fused, then in step 1316 it can again be determinedwhether the X/R is known. If it is known, then the LVF can be calculatedin step 1319. If it is not known, then the X/R can be set equal to,e.g., 4.9.

In step 1321, it can be determined if the LVF is less than 1 and if itis, then the LVF can be set equal to 1. In step 1322 I_(intadj) can bedetermined using the following:

MCCB/ICCB/PCBWith Instantaneous:Iint,adj=LVF*Isym,rms

PCB Without Instantaneous:Iint,adj=LVFp*Isym,rms(½ Cyc)int,adj=LVFasym*Isym,rms(3-8 Cyc)

In step 1323, it can be determined whether the device's symmetricalrating is greater than or equal to I_(intadj), and it can be determinedbased on this evaluation whether the device passed or failed in steps1324 and 1325 respectively. The percent rating can then be determined instep 1326 using the following:% rating=I _(intadj)*100/device rating.

FIG. 14 is a diagram illustrating a process for evaluating the withstandcapabilities of a MVCB in accordance with one embodiment. In step 1328,a determination can be made as to whether the following calculationswill be based on all remote inputs, all local inputs or on a No AC Decay(NACD) ratio. For certain implementations, a calculation can then bemade of the total remote contribution, total local contribution, totalcontribution (I_(intrmssym)), and NACD. If the calculated NACD is equalto zero, then it can be determined that all contributions are local. IfNACD is equal to 1, then it can be determined that all contributions areremote.

If all the contributions are remote, then in step 1332 the remote MF(MFr) can be calculated and I_(int) can be calculated using thefollowing:I _(int)=MFr*I _(intrmssym).

If all the inputs are local, then MFl can be calculated and I_(int) canbe calculated using the following:I _(int)=MFl*I _(intrmssym).

If the contributions are from NACD, then the NACD, MFr, MFl, and AMFlcan be calculated. If AMFl is less than 1, then AMFl can be set equalto 1. I_(int) can then be calculated using the following:I _(int) =AMF1*I _(intrmssym) /S.

In step 1338, the 3-phase device duty cycle can be calculated and thenit can be determined in step 1340, whether the device rating is greaterthan or equal to I_(int). Whether the device passed or failed can thenbe determined in steps 1342 and 1344, respectively. The percent ratingcan be determined in step 1346 using the following:% rating=I _(int)*100/3p device rating.

In other embodiments, it can be determined, in step 1348, whether theuser has selected a fixed MF. If so, then in certain embodiments thepeak duty (crest) can be determined in step 1349 and MFp can be setequal to 2.7 in step 1354. If a fixed MF has not been selected, then thepeak duty (crest) can be calculated in step 1350 and MFp can becalculated in step 1358. In step 1362, the MFp can be used to calculatethe following:I _(mompeak)=MFp*I _(symrms).

In step 1366, it can be determined if the device peak rating (crest) isgreater than or equal to I_(mompeak). It can then be determined whetherthe device passed or failed in steps 1368 and 1370 respectively, and thepercent rating can be calculated as follows:% rating=I _(mompeak)*100/device peak(crest) rating.

In other embodiments, if a fixed MF is selected, then a momentary dutycycle (C&L) can be determined in step 1351 and MFm can be set equal to,e.g., 1.6. If a fixed MF has not been selected, then in step 1352 MFmcan be calculated. MFm can then be used to determine the following:I _(momsym)=MFm*I _(symrms).

It can then be determined in step 1374 whether the device C&L, rmsrating is greater than or equal to I_(momsym). Whether the device passedor failed can then be determined in steps 1376 and 1378 respectively,and the percent rating can be calculated as follows:% rating=I _(momasym)*100/device C&L,rms rating.

Thus, the above methods provide a mean to determine the withstandcapability of various protective devices, under various conditions andusing various standards, using an aged, up to date virtual model of thesystem being monitored.

The influx of massive sensory data, e.g., provided via sensors 104, 106,and 108, intelligent filtration of this dense stream of data intomanageable and easily understandable knowledge. For example, asmentioned, it is important to be able to assess the real-time ability ofthe power system to provide sufficient generation to satisfy the systemload requirements and to move the generated energy through the system tothe load points. Conventional systems do not make use of an on-line,real-time system snap shot captured by a real-time data acquisitionplatform to perform real time system availability evaluation.

FIG. 15 is a flow chart illustrating an example process for analyzingthe reliability of an electrical power distribution and transmissionsystem in accordance with one embodiment. First, in step 1502,reliability data can be calculated and/or determined. The inputs used instep 1502 can comprise power flow data, e.g., network connectivity,loads, generations, cables/transformer impedances, etc., which can beobtained from the predicted values generated in step 1008, reliabilitydata associated with each power system component, lists of contingenciesto be considered, which can vary by implementation including by region,site, etc., customer damage (load interruptions) costs, which can alsovary by implementation, and load duration curve information. Otherinputs can include failure rates, repair rates, and requiredavailability of the system and of the various components.

In step 1504 a list of possible outage conditions and contingencies canbe evaluated including loss of utility power supply, generators, UPS,and/or distribution lines and infrastructure. In step 1506, a power flowanalysis for monitored system 102 under the various contingencies can beperformed. This analysis can include the resulting failure rates, repairrates, cost of interruption or downtime versus the required systemavailability, etc. In step 1510, it can be determined if the system isoperating in a deficient state when confronted with a specificcontingency. If it is, then is step 1512, the impact on the system, loadinterruptions, costs, failure duration, system unavailability, etc. canall be evaluated.

After the evaluation of step 1512, or if it is determined that thesystem is not in a deficient state in step 1510, then it can bedetermined if further contingencies need to be evaluated. If so, thenthe process can revert to step 1506 and further contingencies can beevaluated. If no more contingencies are to be evaluated, then a reportcan be generated in step 1514. The report can include a system summary,total and detailed reliability indices, system availability, etc. Thereport can also identify system bottlenecks are potential problem areas.

The reliability indices can be based on the results of credible systemcontingencies involving both generation and transmission outages. Thereliability indices can include load point reliability indices, branchreliability indices, and system reliability indices. For example,various load/bus reliability indices can be determined such asprobability and frequency of failure, expected load curtailed, expectedenergy not supplied, frequency of voltage violations, reactive powerrequired, and expected customer outage cost. The load point indices canbe evaluated for the major load buses in the system and can be used insystem design for comparing alternate system configurations andmodifications.

Overall system reliability indices can include power interruption index,power supply average MW curtailment, power supply disturbance index,power energy curtailment index, severity index, and system availability.For example, the individual load point indices can be aggregated toproduce a set of system indices. These indices are indicators of theoverall adequacy of the composite system to meet the total system loaddemand and energy requirements and can be extremely useful for thesystem planner and management, allowing more informed decisions to bemade both in planning and in managing the system.

The various analysis and techniques can be broadly classified as beingeither Monte Carlo simulation or Contingency Enumeration. The processcan also use AC, DC and fast linear network power flow solutionstechniques and can support multiple contingency modeling, multiple loadlevels, automatic or user-selected contingency enumeration, use avariety of remedial actions, and provides sophisticated reportgeneration.

The analysis of step 1506 can include adequacy analysis of the powersystem being monitored based on a prescribed set of criteria by whichthe system must be judged as being in the success or failed state. Thesystem is considered to be in the failed state if the service at loadbuses is interrupted or its quality becomes unacceptable, i.e., if thereare capacity deficiency, overloads, and/or under/over voltages

Various load models can be used in the process of FIG. 15 includingmulti-step load duration curve, curtailable and Firm, and CustomerOutage Cost models. Additionally, various remedial actions can beproscribed or even initiated including MW and MVAR generation control,generator bus voltage control, phase shifter adjustment, MW generationrescheduling, and load curtailment (interruptible and firm).

In other embodiments, the effect of other variables, such as the weatherand human error can also be evaluated in conjunction with the process ofFIG. 15 and indices can be associated with these factors. For example,FIG. 16 is a flow chart illustrating an example process for analyzingthe reliability of an electrical power distribution and transmissionsystem that takes weather information into account in accordance withone embodiment. Thus, in step 1602, real-time weather data can bereceived, e.g., via a data feed such as an XML feed from NationalOceanic and Atmosphere Administration (NOAA). In step 1604, this datacan be converted into reliability data that can be used in step 1502.

It should also be noted that National Fire Protection Association (NFPA)and the Occupational Safety and Health Association (OSHA) have mandatedthat facilities comply with proper workplace safety standards andconduct Arc Flash studies in order to determine the incident energy,protection boundaries and PPE levels needed to be worn by technicians.Unfortunately, conventional approaches/systems for performing suchstudies do not provide a reliable means for the real-time prediction ofthe potential energy released (in calories per centimeter squared) foran arc flash event. Moreover, no real-time system exists that canpredict the required personal protective equipment (PPE) required tosafely perform repairs as required by NFPA 70E and IEEE 1584.

When a fault in the system being monitored contains an arc, the heatreleased can damage equipment and cause personal injury. It is thelatter concern that brought about the development of the heat exposureprograms referred to above. The power dissipated in the arc radiates tothe surrounding surfaces. The further away from the arc the surface is,the less the energy is received per unit area.

As noted above, conventional approaches are based on highly specializedstatic simulation models that are rigid and non-reflective of thefacilities operational status at the time a technician may be needed toconduct repairs on electrical equipment. But the PPE level required forthe repair, or the safe protection boundary may change based on theactual operational status of the facility and alignment of the powerdistribution system at the time repairs are needed. Therefore, a staticmodel does not provide the real-time analysis that can be critical foraccurate PPE level determination. This is because static systems cannotadjust to the many daily changes to the electrical system that occur ata facility, e.g., motors and pumps may be on or off, on-site generationstatus may have changed by having diesel generators on-line, utilityelectrical feed may also change, etc., nor can they age with thefacility to accurately predict the required PPE levels.

Accordingly, existing systems rely on exhaustive studies to be performedoff-line by a power system engineer or a design professional/specialist.Often the specialist must manually modify a simulation model so that itis reflective of the proposed facility operating condition and thenconduct a static simulation or a series of static simulations in orderto come up with recommended safe working distances, energy calculationsand PPE levels. But such a process is not timely, accurate norefficient, and as noted above can be quite costly.

Using the systems and methods described herein a logical model of afacility electrical system can be integrated into a real-timeenvironment, with a robust AC Arc Flash simulation engine (systemmodeling engine 124), a data acquisition system (data acquisition hub112), and an automatic feedback system (calibration engine 134) thatcontinuously synchronizes and calibrates the logical model to the actualoperational conditions of the electrical system. The ability to re-alignthe simulation model in real-time so that it mirrors the real facilityoperating conditions, coupled with the ability to calibrate and age themodel as the real facility ages, as describe above, provides a desirableapproach to predicting PPE levels, and safe working conditions at theexact time the repairs are intended to be performed. Accordingly,facility management can provide real-time compliance with, e.g., NFPA70E and IEEE 1584 standards and requirements.

FIG. 17 is a diagram illustrating an example process for predicting inreal-time various parameters associated with an alternating current (AC)arc flash incident. These parameters can include for example, the arcflash incident energy, arc flash protection boundary, and requiredPersonal Protective Equipment (PPE) levels, e.g., in order to complywith NFPA-70E and IEEE-1584. First, in step 1702, updated virtual modeldata can be obtained for the system being model, e.g., the updated dataof step 1006, and the operating modes for the system can be determined.In step 1704, an AC 3-phase short circuit analysis can be performed inorder to obtain bolted fault current values for the system. In step1706, e.g., IEEE 1584 equations can be applied to the bolted faultvalues and any corresponding arcing currents can be calculated in step1708.

The ratio of arc current to bolted current can then be used, in step1710, to determine the arcing current in a specific protective device,such as a circuit breaker or fuse. A coordinated time-current curveanalysis can be performed for the protective device in step 1712. Instep 1714, the arcing current in the protective device and the timecurrent analysis can be used to determine an associated fault clearingtime, and in step 1716 a corresponding arc energy can be determinedbased on, e.g., IEEE 1584 equations applied to the fault clearing timeand arcing current.

In step 1718, the 100% arcing current can be calculated and for systemsoperating at less than 1 kV the 85% arcing current can also becalculated. In step 1720, the fault clearing time in the protectivedevice can be determined at the 85% arcing current level. In step 1722,e.g., IEEE 1584 equations can be applied to the fault clearing time(determined in step 1720) and the arcing current to determine the 85%arc energy level, and in step 1724 the 100% arcing current can becompared with the 85% arcing current, with the higher of the two beingselected. IEEE 1584 equations, for example, can then be applied to theselected arcing current in step 1726 and the PPE level and boundarydistance can be determined in step 1728. In step 1730, these values canbe output, e.g., in the form of a display or report.

In other embodiments, using the same or a similar procedure asillustrated in FIG. 17, the following evaluations can be made inreal-time and based on an accurate, e.g., aged, model of the system:

-   -   Arc Flash Exposure based on IEEE 1584;    -   Arc Flash Exposure based on NFPA 70E;    -   Network-Based Arc Flash Exposure on AC Systems/Single Branch        Case;    -   Network-Based Arc Flash Exposure on AC Systems/Multiple Branch        Cases;    -   Network Arc Flash Exposure on DC Networks;    -   Exposure Simulation at Switchgear Box, MCC Box, Open Area and        Cable Grounded and Ungrounded;    -   Calculate and Select Controlling Branch(s) for Simulation of Arc        Flash;    -   Test Selected Clothing;    -   Calculate Clothing Required;    -   Calculate Safe Zone with Regard to User Defined Clothing        Category;    -   Simulated Art Heat Exposure at User Selected locations;    -   User Defined Fault Cycle for 3-Phase and Controlling Branches;    -   User Defined Distance for Subject;    -   100% and 85% Arcing Current;    -   100% and 85% Protective Device Time;    -   Protective Device Setting Impact on Arc Exposure Energy;    -   User Defined Label Sizes;    -   Attach Labels to One-Line Diagram for User Review;    -   Plot Energy for Each Bus;    -   Write Results into Excel;    -   View and Print Graphic Label for User Selected Bus(s); and    -   Work permit.

With the insight gained through the above methods, appropriateprotective measures, clothing and procedures can be mobilized tominimize the potential for injury should an arc flash incident occur.Facility owners and operators can efficiently implement a real-timesafety management system that is in compliance with NFPA 70E and IEEE1584 guidelines.

FIG. 18 is a flow chart illustrating an example process for real-timeanalysis of the operational stability of an electrical powerdistribution and transmission system in accordance with one embodiment.The ability to predict, in real-time, the capability of a power systemto maintain stability and/or recover from various contingency events anddisturbances without violating system operational constraints isimportant. This analysis determines the real-time ability of the powersystem to: 1. sustain power demand and maintain sufficient active andreactive power reserve to cope with ongoing changes in demand and systemdisturbances due to contingencies, 2. operate safely with minimumoperating cost while maintaining an adequate level of reliability, and3. provide an acceptably high level of power quality (maintainingvoltage and frequency within tolerable limits) when operating undercontingency conditions.

In step 1802, the dynamic time domain model data can be updated tore-align the virtual system model in real-time so that it mirrors thereal operating conditions of the facility. The updates to the domainmodel data coupled with the ability to calibrate and age the virtualsystem model of the facility as it ages (i.e., real-time condition ofthe facility), as describe above, provides a desirable approach topredicting the operational stability of the electrical power systemoperating under contingency situations. That is, these updates accountfor the natural aging effects of hardware that comprise the totalelectrical power system by continuously synchronizing and calibratingboth the control logic used in the simulation and the actual operatingconditions of the electrical system

The domain model data includes data that is reflective of both thestatic and non-static (rotating) components of the system. Staticcomponents are those components that are assumed to display no changesduring the time in which the transient contingency event takes place.Typical time frames for disturbance in these types of elements rangefrom a few cycles of the operating frequency of the system up to a fewseconds. Examples of static components in an electrical system includebut are not limited to transformers, cables, overhead lines, reactors,static capacitors, etc. Non-static (rotating) components encompasssynchronous machines including their associated controls (exciters,governors, etc), induction machines, compensators, motor operated valves(MOV), turbines, static var compensators, fault isolation units (FIU),static automatic bus transfer (SABT) units, etc. These various types ofnon-static components can be simulated using various techniques. Forexample:

-   -   For Synchronous Machines: thermal (round rotor) and hydraulic        (salient pole) units can be both simulated either by using a        simple model or by the most complete two-axis including damper        winding representation.    -   For Induction Machines: a complete two-axis model can be used.        Also it is possible to model them by just providing the testing        curves (current, power factor, and torque as a function of        speed).    -   For Motor Operated Valves (MOVs): Two modes of MOV operation are        of interest, namely, opening and closing operating modes. Each        mode of operation consists of five distinct stages, a) start, b)        full speed, c) unseating, d) travel, and e) stall. The system        supports user-defined model types for each of the stages. That        is, “start” may be modeled as a constant current while “full        speed” may be modeled by constant power. This same flexibility        exists for all five distinct stages of the closing mode.    -   For AVR and Excitation Systems: There are a number of models        ranging form rotating (DC and AC) and analogue to static and        digital controls. Additionally, the system offers a user-defined        modeling capability, which can be used to define a new        excitation model.    -   For Governors and Turbines: The system is designed to address        current and future technologies including but not limited to        hydraulic, diesel, gas, and combined cycles with mechanical        and/or digital governors.    -   For Static Var Compensators (SVCs): The system is designed to        address current and future technologies including a number of        solid-state (thyristor) controlled SVC's or even the saturable        reactor types.    -   For Fault Isolation Units (FIUs): The system is designed to        address current and future technologies of FIUs also known as        Current Limiting Devices, are devices installed between the        power source and loads to limit the magnitude of fault currents        that occur within loads connected to the power distribution        networks.    -   For Static Automatic Bus Transfers (SABT): The system is        designed to address current and future technologies of SABT        (i.e., solid-state three phase, dual position, three-pole        switch, etc.)

In one embodiment, the time domain model data includes “built-in”dynamic model data for exciters, governors, transformers, relays,breakers, motors, and power system stabilizers (PSS) offered by avariety of manufactures. For example, dynamic model data for theelectrical power system may be OEM manufacturer supplied control logicfor electrical equipment such as automatic voltage regulators (AVR),governors, under load tap changing transformers, relays, breakersmotors, etc. In another embodiment, in order to cope with recentadvances in power electronic and digital controllers, the time domainmodel data includes “user-defined” dynamic modeling data that is createdby an authorized system administrator in accordance with user-definedcontrol logic models. The user-defined models interacts with the virtualsystem model of the electrical power system through “InterfaceVariables” 1816 that are created out of the user-defined control logicmodels. For example, to build a user-defined excitation model, thecontrols requires that generator terminal voltage to be measured andcompared with a reference quantity (voltage set point). Based on thespecific control logic of the excitation and AVR, the model would thencompute the predicted generator field voltage and return that value backto the application. The user-defined modeling supports a large number ofpre-defined control blocks (functions) that are used to assemble therequired control systems and put them into action in a real-timeenvironment for assessing the strength and security of the power system.In still another embodiment, the time domain model data includes bothbuilt-in dynamic model data and user-defined model data.

Moving on to step 1804, a contingency event can be chosen out of adiverse list of contingency events to be evaluated. That is, theoperational stability of the electrical power system can be assessedunder a number of different contingency event scenarios including butnot limited to a singular event contingency or multiple eventcontingencies (that are simultaneous or sequenced in time). In oneembodiment, the contingency events assessed are manually chosen by asystem administrator in accordance with user requirements. In anotherembodiment, the contingency events assessed are automatically chosen inaccordance with control logic that is dynamically adaptive to pastobservations of the electrical power system. That is the control logic“learns” which contingency events to simulate based on past observationsof the electrical power system operating under various conditions.

Some examples of contingency events include but are not limited to:

-   -   Application/removal of three-phase fault.    -   Application/removal of phase-to-ground fault    -   Application/removal of phase-phase-ground fault.    -   Application/removal of phase-phase fault.    -   Branch Addition.    -   Branch Tripping    -   Starting Induction Motor.    -   Stopping Induction Motor    -   Shunt Tripping.    -   Shunt Addition (Capacitor and/or Induction)    -   Generator Tripping.    -   SVC Tripping.    -   Impact Loading (Load Changing Mechanical Torque on Induction        Machine.    -   With this option it is actually possible to turn an induction        motor to an induction generator)    -   Loss of Utility Power Supply/Generators/UPS/Distribution        Lines/System    -   Infrastructure    -   Load Shedding

In step 1806, a transient stability analysis of the electrical powersystem operating under the various chosen contingencies can beperformed. This analysis can include identification of system weaknessesand insecure contingency conditions. That is, the analysis can predict(forecast) the system's ability to sustain power demand, maintainsufficient active and reactive power reserve, operate safely withminimum operating cost while maintaining an adequate level ofreliability, and provide an acceptably high level of power quality whilebeing subjected to various contingency events. The results of theanalysis can be stored by an associative memory engine 1818 during step1814 to support incremental learning about the operationalcharacteristics of the system. That is, the results of the predictions,analysis, and real-time data may be fed, as needed, into the associativememory engine 1818 for pattern and sequence recognition in order tolearn about the logical realities of the power system. In certainembodiments, engine 1818 can also act as a pattern recognition engine ora Hierarchical Temporal Memory (HTM) engine. Additionally, concurrentinputs of various electrical, environmental, mechanical, and othersensory data can be used to learn about and determine normality andabnormality of business and plant operations to provide a means ofunderstanding failure modes and give recommendations.

In step 1810, it can be determined if the system is operating in adeficient state when confronted with a specific contingency. If it is,then in step 1812, a report is generated providing a summary of theoperational stability of the system. The summary may include generalpredictions about the total security and stability of the system and/ordetailed predictions about each component that makes up the system.

Alternatively, if it is determined that the system is not in a deficientstate in step 1810, then step 1808 can determine if furthercontingencies needs to be evaluated. If so, then the process can revertto step 1806 and further contingencies can be evaluated.

The results of real-time simulations performed in accordance with FIG.18 can be communicated in step 1812 via a report, such as a print out ordisplay of the status. In addition, the information can be reported viaa graphical user interface (thick or thin client) that illustrated thevarious components of the system in graphical format. In suchembodiments, the report can simply comprise a graphical indication ofthe security or insecurity of a component, subsystem, or system,including the whole facility. The results can also be forwarded toassociative memory engine 1818, where they can be stored and madeavailable for predictions, pattern/sequence recognition and ability toimagine, e.g., via memory agents or other techniques, some of which aredescribe below, in step 1820.

The process of FIG. 18 can be applied to a number of needs including butnot limited to predicting system stability due to: Motor starting andmotor sequencing, an example is the assessment of adequacy of a powersystem in emergency start up of auxiliaries; evaluation of theprotections such as under frequency and under-voltage load sheddingschemes, example of this is allocation of required load shedding for apotential loss of a power generation source; determination of criticalclearing time of circuit breakers to maintain stability; anddetermination of the sequence of protective device operations andinteractions.

FIG. 19 is a flow chart illustrating an example process for conducting areal-time power capacity assessment of an electrical power distributionand transmission system, in accordance with one embodiment. Thestability of an electrical power system can be classified into two broadcategories: transient (angular) stability and voltage stability (i.e.,power capacity). Voltage stability refers to the electrical system'sability to maintain acceptable voltage profiles under different systemtopologies and load changes (i.e., contingency events). That is, voltagestability analyses determine bus voltage profiles and power flows in theelectrical system before, during, and immediately after a majordisturbance. Generally speaking, voltage instability stems from theattempt of load dynamics to restore power consumption beyond thecapability of the combined transmission and generation system. Onefactor that comes into play is that unlike active power, reactive powercannot be transported over long distances. As such, a power system richin reactive power resources is less likely to experience voltagestability problems. Overall, the voltage stability of a power system isof paramount importance in the planning and daily operation of anelectrical system.

Traditionally, transient stability has been the main focus of powersystem professionals. However, with the increased demand for electricalenergy and the regulatory hurdles blocking the expansion of existingpower systems, the occurrences of voltage instability has becomeincreasingly frequent and therefore has gained increased attention frompower system planners and power system facility operators. The abilityto learn, understand and make predictions about available power systemcapacity and system susceptibility to voltage instability, in real-timewould be beneficial in generating power trends for forecasting purposes.

In step 1902, the voltage stability modeling data for the componentscomprising the electrical system can be updated to re-align the virtualsystem model in “real-time” so that it mirrors the real operatingconditions of the facility. These updates to the voltage stabilitymodeling data coupled with the ability to calibrate and age the virtualsystem model of the facility as it ages (i.e., real-time condition ofthe facility), as describe above, provides a desirable approach topredicting occurrences of voltage instability (or power capacity) in theelectrical power system when operating under contingency situations.That is, these updates account for the natural aging effects of hardwarethat comprise the total electrical power system by continuouslysynchronizing and calibrating both the control logic used in thesimulation and the actual operating conditions of the electrical system

The voltage stability modeling data includes system data that has directinfluence on the electrical system's ability to maintain acceptablevoltage profiles when the system is subjected to various contingencies,such as when system topology changes or when the system encounters powerload changes. Some examples of voltage stability modeling data are loadscaling data, generation scaling data, load growth factor data, loadgrowth increment data, etc.

In one embodiment, the voltage stability modeling data includes“built-in” data supplied by an OEM manufacturer of the components thatcomprise the electrical equipment. In another embodiment, in order tocope with recent advances power system controls, the voltage stabilitydata includes “user-defined” data that is created by an authorizedsystem administrator in accordance with user-defined control logicmodels. The user-defined models interact with the virtual system modelof the electrical power system through “Interface Variables” 1916 thatare created out of the user-defined control logic models. In stillanother embodiment, the voltage stability modeling data includes acombination of both built-in model data and user-defined model data

Moving on to step 1904, a contingency event can be chosen out of adiverse list of contingency events to be evaluated. That is, the voltagestability of the electrical power system can be assessed under a numberof different contingency event scenarios including but not limited to asingular event contingency or multiple event contingencies (that aresimultaneous or sequenced in time). In one embodiment, the contingencyevents assessed are manually chosen by a system administrator inaccordance with user requirements. In another embodiment, thecontingency events assessed are automatically chosen in accordance withcontrol logic that is dynamically adaptive to past observations of theelectrical power system. That is the control logic “learns” whichcontingency events to simulate based on past observations of theelectrical power system operating under various conditions. Someexamples of contingency events include but are not limited to: loss ofutility supply to the electrical system, loss of available powergeneration sources, system load changes/fluctuations, loss ofdistribution infrastructure associated with the electrical system, etc.

In step 1906, a voltage stability analysis of the electrical powersystem operating under the various chosen contingencies can beperformed. This analysis can include a prediction (forecast) of thetotal system power capacity, available system power capacity andutilized system power capacity of the electrical system of theelectrical system under various contingencies. That is, the analysis canpredict (forecast) the electrical system's ability to maintainacceptable voltage profiles during load changes and when the overallsystem topology undergoes changes. The results of the analysis can bestored by an associative memory engine 1918 during step 1914 to supportincremental learning about the power capacity characteristics of thesystem. That is, the results of the predictions, analysis, and real-timedata may be fed, as needed, into the associative memory engine 1918 forpattern and sequence recognition in order to learn about the voltagestability of the electrical system in step 1920. Additionally,concurrent inputs of various electrical, environmental, mechanical, andother sensory data can be used to learn about and determine normalityand abnormality of business and plant operations to provide a means ofunderstanding failure modes and give recommendations.

In step 1910, it can be determined if there is voltage instability inthe system when confronted with a specific contingency. If it is, thenin step 1912, a report is generated providing a summary of the specificsand source of the voltage instability. The summary may include generalpredictions about the voltage stability of the overall system and/ordetailed predictions about each component that makes up the system.

Alternatively, if it is determined that the system is not in a deficientstate in step 1910, then step 1908 can determine if furthercontingencies needs to be evaluated. If so, then the process can revertto step 1906 and further contingencies can be evaluated.

The results of real-time simulations performed in accordance with FIG.19 can be communicated in step 1912 via a report, such as a print out ordisplay of the status. In addition, the information can be reported viaa graphical user interface (thick or thin client) that illustrated thevarious components of the system in graphical format. In suchembodiments, the report can simply comprise a graphical indication ofthe capacity of a subsystem or system, including the whole facility. Theresults can also be forwarded to associative memory engine 1918, wherethey can be stored and made available for predictions, pattern/sequencerecognition and ability to imagine, e.g., via memory agents or othertechniques, some of which are describe below, in step 1920

The systems and methods described above can also be used to providereports (step 1912) on, e.g., total system electrical capacity, totalsystem capacity remaining, total capacity at all busbars and/orprocesses, total capacity remaining at all busbars and/or processes,total system loading, loading at each busbar and/or process, etc.

Thus, the process of FIG. 19 can receive input data related to powerflow, e.g., network connectivity, loads, generations,cables/transformers, impedances, etc., power security, contingencies,and capacity assessment model data and can produce as outputs datarelated to the predicted and designed total system capacity, availablecapacity, and present capacity. This information can be used to makemore informed decisions with respect to management of the facility.

FIG. 20 is a flow chart illustrating an example process for performingreal-time harmonics analysis of an electrical power distribution andtransmission system, in accordance with one embodiment. As technologicaladvances continue to be made in the field of electronic devices, therehas been particular emphasis on the development of energy savingfeatures. Electricity is now used quite differently from the way it usedbe used with new generations of computers and peripherals using verylarge-scale integrated circuitry operating at low voltages and currents.Typically, in these devices, the incoming alternating current (AC)voltage is diode rectified and then used to charge a large capacitor.The electronic device then draws direct current (DC) from the capacitorin short non-linear pulses to power its internal circuitry. Thissometimes causes harmonic distortions to arise in the load current,which may result in overheated transformers and neutrals, as well astripped circuit breakers in the electrical system.

The inherent risks (to safety and the operational life of componentscomprising the electrical system) that harmonic distortions poses toelectrical systems have led to the inclusion of harmonic distortionanalysis as part of traditional power analysis. Metering and sensorpackages are currently available to monitor harmonic distortions withinan electrical system. However, it is not feasible to fully sensor out anelectrical system at all possible locations due to cost and the physicalaccessibility limitations in certain parts of the system. Therefore,there is a need for techniques that predict, through real-timesimulation, the sources of harmonic distortions within an electricalsystem, the impacts that harmonic distortions have or may have, and whatsteps (i.e., harmonics filtering) may be taken to minimize or eliminateharmonics from the system.

Currently, there are no reliable techniques for predicting, inreal-time, the potential for periodic non-sinusoidal waveforms (i.e.harmonic distortions) to occur at any location within an electricalsystem powered with sinusoidal voltage. In addition, existing techniquesdo not take into consideration the operating conditions and topology ofthe electrical system or utilizes a virtual system model of the systemthat “ages” with the actual facility or its current condition. Moreover,no existing technique combines real-time power quality meter readingsand predicted power quality readings for use with a pattern recognitionsystem such as an associative memory machine learning system to predictharmonic distortions in a system due to changes in topology or pooroperational conditions within an electrical system.

The process, described herein, provides a harmonics analysis solutionthat uses a real-time snap shot captured by a data acquisition system toperform a real-time system power quality evaluation at all locationsregardless of power quality metering density. This process integrates,in real-time, a logical simulation model (i.e., virtual system model) ofthe electrical system, a data acquisition system, and power systemsimulation engines with a logic based approach to synchronize thelogical simulation model with conditions at the real electrical systemto effectively “age” the simulation model along with the actualelectrical system. Through this approach, predictions about harmonicdistortions in an electrical system may be accurately calculated inreal-time. Condensed, this process works by simulating harmonicdistortions in an electrical system through subjecting a real-timeupdated virtual system model of the system to one or more simulatedcontingency situations.

In step 2002, the harmonic frequency modeling data for the componentscomprising the electrical system can be updated to re-align the virtualsystem model in “real-time” so that it mirrors the real operatingconditions of the facility. These updates to the harmonic frequencymodeling data coupled with the ability to calibrate and age the virtualsystem model of the facility as it ages (i.e., real-time condition ofthe facility), as describe above, provides a desirable approach topredicting occurrences of harmonic distortions within the electricalpower system when operating under contingency situations. That is, theseupdates account for the natural aging effects of hardware that comprisethe total electrical power system by continuously synchronizing andcalibrating both the control logic used in the simulation and the actualoperating conditions of the electrical system.

Harmonic frequency modeling data has direct influence over how harmonicdistortions are simulated during a harmonics analysis. Examples of datathat is included with the harmonic frequency modeling data include: IEEE519 and/or Mil 1399 compliant system simulation data,generator/cable/motor skin effect data, transformer phase shifting data,generator impedance data, induction motor impedance data, etc.

Moving on to step 2004, a contingency event can be chosen out of adiverse list of contingency events to be evaluated. That is, theelectrical system can be assessed for harmonic distortions under anumber of different contingency event scenarios including but notlimited to a singular event contingency or multiple event contingencies(that are simultaneous or sequenced in time). In one embodiment, thecontingency events assessed are manually chosen by a systemadministrator in accordance with user requirements. In anotherembodiment, the contingency events assessed are automatically chosen inaccordance with control logic that is dynamically adaptive to pastobservations of the electrical power system. That is the control logic“learns” which contingency events to simulate based on past observationsof the electrical power system operating under various conditions. Someexamples of contingency events include but are not limited to additions(bringing online) and changes of equipment that effectuate a non-linearload on an electrical power system (e.g., as rectifiers, arc furnaces,AC/DC drives, variable frequency drives, diode-capacitor input powersupplies, uninterruptible power supplies, etc.) or other equipment thatdraws power in short intermittent pulses from the electrical powersystem.

Continuing with FIG. 20, in step 2006, a harmonic distortion analysis ofthe electrical power system operating under the various chosencontingencies can be performed. This analysis can include predictions(forecasts) of different types of harmonic distortion data at variouspoints within the system. Harmonic distortion data may include but arenot limited to:

-   -   Wave-shape Distortions/Oscillations data    -   Parallel and Series Resonant Condition data    -   Total Harmonic Distortion Level data (both Voltage and Current        type)    -   Data on the true RMS system loading of lines, transformers,        capacitors, etc.    -   Data on the Negative Sequence Harmonics being absorbed by the AC        motors    -   Transformer K-Factor Level data    -   Frequency scan at positive, negative, and zero angle response        throughout the entire scanned spectrum in the electrical system.

That is, the harmonics analysis can predict (forecast) variousindicators (harmonics data) of harmonic distortions occurring within theelectrical system as it is being subjected to various contingencysituations. The results of the analysis can be stored by an associativememory engine 2016 during step 2014 to support incremental learningabout the harmonic distortion characteristics of the system. That is,the results of the predictions, analysis, and real-time data may be fed,as needed, into the associative memory engine 2016 for pattern andsequence recognition in order to learn about the harmonic distortionprofile of the electrical system in step 2018. Additionally, concurrentinputs of various electrical, environmental, mechanical, and othersensory data can be used to learn about and determine normality andabnormality of business and plant operations to provide a means ofunderstanding failure modes and give recommendations.

In step 2010, it can be determined if there are harmonic distortionswithin the system when confronted with a specific contingency. If it is,then in step 2012, a report is generated providing a summary ofspecifics regarding the characteristics and sources of the harmonicdistortions. The summary may include forecasts about the different typesof harmonic distortion data (e.g., Wave-shape Distortions/Oscillationsdata, Parallel and Series Resonant Condition data, etc.) generated atvarious points throughout the system. Additionally, through theseforecasts, the associative memory engine 2016 can make predictions aboutthe natural oscillation response(s) of the facility and compare thosepredictions with the harmonic components of the non-linear loads thatare fed or will be fed from the system as indicated form the dataacquisition system and power quality meters. This will give anindication of what harmonic frequencies that the potential resonantconditions lie at and provide facility operators with the ability toeffectively employ a variety of harmonic mitigation techniques (e.g.,addition of harmonic filter banks, etc.)

Alternatively, if it is determined that the system is not in a deficientstate in step 2010, then step 2008 can determine if furthercontingencies needs to be evaluated. If so, then the process can revertto step 2006 and further contingencies can be evaluated.

The results of real-time simulations performed in accordance with FIG.20 can be communicated in step 2012 via a report, such as a print out ordisplay of the status. In addition, the information can be reported viaa graphical user interface (thick or thin client) that illustrated thevarious components of the system in graphical format. In suchembodiments, the report can simply comprise a graphical indication ofthe harmonic status of subsystem or system, including the wholefacility. The results can also be forwarded to associative memory engine2016, where they can be stored and made available for predictions,pattern/sequence recognition and ability to imagine, e.g., via memoryagents or other techniques, some of which are describe below, in step2018

Thus, the process of FIG. 20 can receive input data related to powerflow, e.g., network connectivity, loads, generations,cables/transformers, impedances, etc., power security, contingencies,and can produce as outputs data related to Point Specific Power QualityIndices, Branch Total Current Harmonic Distortion Indices, Bus and NodeTotal Voltage Harmonic Distortion Indices, Frequency Scan Indices forPositive Negative and Zero Sequences, Filter(s) Frequency AngleResponse, Filter(s) Frequency Impedance Response, and Voltage andCurrent values over each filter elements (r, xl, xc).

FIG. 21 is a diagram illustrating how the HTM Pattern Recognition andMachine Learning Engine works in conjunction with the other elements ofthe analytics system to make predictions about the operational aspectsof a monitored system, in accordance with one embodiment. As depictedherein, the HTM Pattern Recognition and Machine Learning Engine 551 ishoused within an analytics server 116 and communicatively connected viaa network connection 114 with a data acquisition hub 112, a clientterminal 128 and a virtual system model database 526. The virtual systemmodel database 526 is configured to store the virtual system model ofthe monitored system. The virtual system model is constantly updatedwith real-time data from the data acquisition hub 112 to effectivelyaccount for the natural aging effects of the hardware that comprise thetotal monitored system, thus, mirroring the real operating conditions ofthe system. This provides a desirable approach to predicting theoperational aspects of the monitored power system operating undercontingency situations.

The HTM Machine Learning Engine 551 is configured to store and processpatterns observed from real-time data fed from the hub 112 and predicteddata output from a real-time virtual system model of the monitoredsystem. These patterns can later be used by the HTM Engine 551 to makereal-time predictions (forecasts) about the various operational aspectsof the system.

The data acquisition hub 112 is communicatively connected via dataconnections 110 to a plurality of sensors that are embedded throughout amonitored system 102. The data acquisition hub 112 may be a standaloneunit or integrated within the analytics server 116 and can be embodiedas a piece of hardware, software, or some combination thereof. In oneembodiment, the data connections 110 are “hard wired” physical dataconnections (e.g., serial, network, etc.). For example, a serial orparallel cable connection between the sensors and the hub 112. Inanother embodiment, the data connections 110 are wireless dataconnections. For example, a radio frequency (RF), BLUETOOTH™, infraredor equivalent connection between the sensor and the hub 112.

Examples of a monitored system includes machinery, factories, electricalsystems, processing plants, devices, chemical processes, biologicalsystems, data centers, aircraft carriers, and the like. It should beunderstood that the monitored system can be any combination ofcomponents whose operations can be monitored with conventional sensorsand where each component interacts with or is related to at least oneother component within the combination.

Continuing with FIG. 21, the client 128 is typically a conventional“thin-client” or “thick client” computing device that may utilize avariety of network interfaces (e.g., web browser, CITRIX™, WINDOWSTERMINAL SERVICES™, telnet, or other equivalent thin-client terminalapplications, etc.) to access, configure, and modify the sensors (e.g.,configuration files, etc.), analytics engine (e.g., configuration files,analytics logic, etc.), calibration parameters (e.g., configurationfiles, calibration parameters, etc.), virtual system modeling engine(e.g., configuration files, simulation parameters, etc.) and virtualsystem model of the system under management (e.g., virtual system modeloperating parameters and configuration files). Correspondingly, in oneembodiment, the data from the various components of the monitored systemand the real-time predictions (forecasts) about the various operationalaspects of the system can be displayed on a client 128 display panel forviewing by a system administrator or equivalent. In another embodiment,the data may be summarized in a hard copy report 2102.

As discussed above, the HTM Machine Learning Engine 551 is configured towork in conjunction with a real-time updated virtual system model of themonitored system to make predictions (forecasts) about certainoperational aspects of the monitored system when it is subjected to acontingency event. For example, where the monitored system is anelectrical power system, in one embodiment, the HTM Machine LearningEngine 551 can be used to make predictions about the operationalreliability of an electrical power system in response to contingencyevents such as a loss of power to the system, loss of distributionlines, damage to system infrastructure, changes in weather conditions,etc. Examples of indicators of operational reliability include but arenot limited to failure rates, repair rates, and required availability ofthe power system and of the various components that make up the system.

In another embodiment, the operational aspects relate to an arc flashdischarge contingency event that occurs during the operation of thepower system. Examples of arc flash related operational aspects includebut are not limited to quantity of energy released by the arc flashevent, required personal protective equipment (PPE) for personneloperating within the confines of the system during the arc flash event,and measurements of the arc flash safety boundary area around componentscomprising the power system. In still another embodiment, theoperational aspect relates to the operational stability of the systemduring a contingency event. That is, the system's ability to sustainpower demand, maintain sufficient active and reactive power reserve,operate safely with minimum operating cost while maintaining an adequatelevel of reliability, and provide an acceptably high level of powerquality while being subjected to a contingency event.

In still another embodiment, the operational aspect relates to thevoltage stability of the electrical system immediately after beingsubjected to a major disturbance (i.e., contingency event). Generallyspeaking, voltage instability stems from the attempt of load dynamics torestore power consumption, after the disturbance, in a manner that isbeyond the capability of the combined transmission and generationsystem. Examples of predicted operational aspects that are indicative ofthe voltage stability of an electrical system subjected to a disturbanceinclude the total system power capacity, available system power capacityand utilized system power capacity of the electrical system under beingsubjected to various contingencies. Simply, voltage stability is theability of the system to maintain acceptable voltage profiles whileunder the influence of the disturbances.

In still yet another embodiment, the operational aspect relates toharmonic distortions in the electrical system subjected to a majordisturbance. Harmonic distortions are characterized by non-sinusoidal(non-linear) voltage and current waveforms. Most harmonic distortionsresult from the generation of harmonic currents caused by nonlinear loadsignatures. A nonlinear load is characteristic in products such ascomputers, printers, lighting and motor controllers, and much of today'ssolid-state equipment. With the advent of power semiconductors and theuse of switching power supplies, the harmonics distortion problem hasbecome more severe.

Examples of operational aspects that are indicative of harmonicdistortions include but are not limited to: wave-shapedistortions/oscillations, parallel and series resonance, total harmonicdistortion level, transformer K-Factor levels, true RMS loading oflines/transformers/capacitors, indicators of negative sequence harmonicsbeing absorbed by alternating current (AC) motors,positive/negative/zero angle frequency response, etc.

FIG. 22 is an illustration of the various cognitive layers that comprisethe neocortical catalyst process used by the HTM Pattern Recognition andMachine Learning Engine to analyze and make predictions about theoperational aspects of a monitored system, in accordance with oneembodiment. As depicted herein, the neocortical catalyst process isexecuted by a neocortical model 2202 that is encapsulated by a real-timesensory system layer 2204, which is itself encapsulated by anassociative memory model layer 2206. Each layer is essential to theoperation of the neocortical catalyst process but the key component isstill the neocortical model 2202. The neocortical model 2202 representsthe “ideal” state and performance of the monitored system and it iscontinually updated in real-time by the sensor layer 2204. The sensorylayer 2204 is essentially a data acquisition system comprised of aplurality of sensors imbedded within the monitored system and configuredto provide real-time data feedback to the neocortical model 2202. Theassociative memory layer observes the interactions between theneocortical model 2202 and the real-time sensory inputs from the sensorylayer 2204 to learn and understand complex relationships inherent withinthe monitored system. As the neocortical model 2202 matures over time,the neocortical catalyst process becomes increasingly accurate in makingpredictions about the operational aspects of the monitored system. Thiscombination of the neocortical model 2202, sensory layer 2204 andassociative memory model layer 2206 works together to learn, refine,suggest and predict similarly to how the human neocortex operates.

FIG. 23 is a flow chart illustrating an example process for real-timemodeling of an uninterruptible power supply (UPS) system protecting anelectrical power distribution and/or transmission system, in accordancewith one embodiment. The ability to predict, in real-time, thecapability of a UPS protected power system to maintain stability and/orrecover from various contingency events and disturbances withoutviolating system operational constraints is important. This analysisdetermines the real-time ability of the UPS protected power systemto: 1. sustain power demand and maintain sufficient active and reactivepower reserve to cope with ongoing changes in demand and systemdisturbances due to contingencies, 2. operate safely with minimumoperating cost while maintaining an adequate level of reliability, and3. provide an acceptably high level of power quality (maintainingvoltage and frequency within tolerable limits) when operating undercontingency conditions.

In step 2302, the dynamic time domain model data can be modified withnew UPS control logic model simulation parameters and updated tore-align the virtual system model in real-time so that it mirrors thereal operating conditions of the facility. The modifications to the UPSparameters coupled with the ability to calibrate and age the virtualsystem model of the facility as it ages (i.e., real-time condition ofthe facility) provides a desirable approach to predicting theoperational reliability and stability of the electrical power systemoperating under various user-defined UPS system architectures (UPScontrol logic models) and under various contingency situations. That is,these modifications and updates allow a user to adjust the UPS controllogic parameters used in the contingency event simulation (as a way toevaluate the effectiveness of different variations of UPS control logicmodels at maintaining the operational reliability and stability of theelectrical power system) and to account for the natural aging effects ofhardware that comprise the total electrical power system by continuouslysynchronizing and calibrating the actual operating conditions of theelectrical system.

The domain model data includes data that is reflective of both thestatic and non-static (rotating) components of the UPS control logicmodel and the virtual system model of the electrical power system.Static components are those components that are assumed to display nochanges during the time in which the transient contingency event takesplace. Typical time frames for disturbance in these types of elementsrange from a few cycles of the operating frequency of the system up to afew seconds. Examples of static components in an electrical systeminclude but are not limited to transformers, cables, overhead lines,reactors, static capacitors, etc. Non-static (rotating) componentsencompass synchronous machines including their associated controls(exciters, governors, etc), induction machines, compensators, motoroperated valves (MOV), turbines, static var compensators, faultisolation units (FIU), static automatic bus transfer (SABT) units, etc.These various types of non-static components can be simulated usingvarious techniques.

For example:

-   -   a. For Synchronous Machines (generators and/or motors): thermal        (round rotor) and hydraulic (salient pole) units can be both        simulated either by using a simple model or by the most complete        two-axis including damper winding representation.    -   b. For Induction Machines (motors and/or generators): a complete        two-axis model can be used. Also it is possible to model such        induction machines by providing testing curves for, e.g.,        current, power factor, and torque as a function of speed.    -   c. For Motor Operated Valves (MOVs): A motor operated valve        (MOV) is commonly used in nuclear power plant auxiliary        operation as well as in other industrial installations. Two        modes of MOV operation are of interest, namely, opening and        closing operating modes. Each mode of operation consists of five        distinct stages, a) start, b) full speed, c) unseating, d)        travel, and e) stall. The system can be configured to support        user-defined model types for each of the stages. That is,        “start” can be modeled as a constant current while “full speed”        can be modeled by constant power. This same flexibility exists        for all five distinct stages of the closing mode.    -   d. For Automatic Voltage Regulators (AVRs) and Excitation        Systems: There are a number of models ranging from rotating (DC        and AC) and analogue to static and digital controls.        Additionally, the system can be configured to offer a        user-defined modeling capability, which can be used to define a        new excitation model.    -   e. For Governors and Turbines: The system can be designed to        address current and future technologies including but not        limited to hydraulic, diesel, gas, and combined cycles with        mechanical and/or digital governors.    -   f. For Relays: The systems can be designed to address current        and future technologies including under frequency, under        voltage, over current and impedance types.    -   g. For Static Var Compensators (SVCs): The system is designed to        address current and future technologies including a number of        solid-state (thyristor) controlled SVC's or even the saturable        reactor types.    -   h. For Fault Isolation Units (FIUs): The system can be designed        to address current and future technologies of FIUs also known as        Current Limiting Devices, which are devices installed between        the power source and loads to limit the magnitude of fault        currents that occur within loads connected to the power        distribution networks.    -   i. For Static Automatic Bus Transfers (SABT): The system can be        designed to address current and future technologies of SABT        (i.e., solid-state three phase, dual position, three-pole        switch, etc.)

In one embodiment, in order to assist in the design of the mosteffective UPS solution to protect the electrical system and to cope withnew advances in UPS equipment and system architectures, the time domainmodel data can include UPS control logic parameters from a“user-defined” UPS control logic model. The user-defined UPS controllogic model 2317 interacts with the UPS transient stability simulationengine through “Interface Variables” 2316 that are generated by themodel. Examples of UPS interface variables 2316 include, but are notlimited to, generator voltage values, generator speed values, automaticvoltage regulator (AVR) field voltage values, governor mechanical powervalues, etc. The interface variables 2316 discussed above are providedhere by way of example only, in practice, the interface variables 2316can be any configuration parameter setting for any UPS control elementtype, as long as the control element can be simulated by the UPStransient stability simulation engine. Based on the specific UPS controllogic the UPS transient stability simulation engine is configured tocompute predicted values for the operation of the electrical powersystem under normal and contingency event conditions.

The user-defined UPS control logic modeling function supports a largenumber of pre-defined control blocks (functions) that are used to builda multitude of different variations of UPS control logic models and putthem into action in a real-time environment for assessing theoperational reliability and stability of the electrical power system.

In another embodiment, the dynamic time domain model data step 2302includes “built-in” manufacturer data for the electrical equipment thatcomprise the UPS control elements and electrical power system. Forexample, dynamic time domain model data for the UPS control logic andelectrical power system may be OEM manufacturer supplied control logicfor electrical equipment such as generators, AVRs, governors, under loadtap changing transformers, relays, breakers, motors, etc. In stillanother embodiment, the dynamic time domain model data includes bothuser-defined and built-in dynamic model data.

Moving on to step 2304, a contingency event can be chosen out of adiverse list of contingency events to be evaluated. That is, theoperational reliability and stability of the UPS controls protecting theelectrical power system can be assessed under a number of differentcontingency event scenarios including but not limited to a singularevent contingency or multiple event contingencies (that are simultaneousor sequenced in time). In one embodiment, the contingency eventsassessed are manually chosen by a system administrator in accordancewith user requirements. In another embodiment, the contingency eventsassessed are automatically chosen in accordance with past observationsof the operation of the UPS controls and electrical power system. Thatis the UPS transient stability simulation engine “learns” whichcontingency events to simulate based on past observations of the UPScontrols and electrical power system operating under various conditions.

Some examples of contingency events include but are not limited to:

-   -   Various UPS operation modes    -   UPS failure    -   Various inverter operation modes    -   Inverter failure    -   Application/removal of three-phase fault    -   Application/removal of phase-to-ground fault    -   Application/removal of phase-phase-ground fault    -   Application/removal of phase-phase fault    -   Branch Addition    -   Branch Tripping    -   Starting Induction Motor    -   Stopping Induction Motor    -   Shunt Tripping.    -   Shunt Addition (Capacitor and/or Induction)    -   Generator Tripping    -   SVC Tripping    -   Impact Loading (Load Changing Mechanical Torque on Induction        Machine    -   With this option it is actually possible to turn an induction        motor to an induction generator)    -   Loss of Utility Power Supply/Generators/UPS/Distribution        Lines/System    -   Infrastructure    -   Load Shedding

In step 2306, a transient stability analysis of the UPS controls and theelectrical power system operating under the various chosen contingenciescan be performed. This analysis can include identification of the UPSsystem architecture strengths and weaknesses and any insecurecontingency conditions. That is, the analysis can predict (forecast) theUPS system's ability to sustain power demand, maintain sufficient activeand reactive power reserve, operate safely with minimum operating costwhile maintaining an adequate level of reliability, and provide anacceptably high level of power quality while being subjected to variouscontingency events. The results of the analysis can be stored by anassociative memory engine 2318 during step 2314 to support incrementallearning about the operational characteristics of the UPS controlsinteracting with the electrical power system. That is, the results ofthe predictions, analysis, and real-time data may be fed, as needed,into the associative memory engine 2318 for pattern and sequencerecognition in order to learn about the logical realities of the UPScontrols in protecting the stability and security of the power system.In certain embodiments, engine 2318 can also act as a patternrecognition engine or a Hierarchical Temporal Memory (HTM) engine.Additionally, concurrent inputs of various electrical, environmental,mechanical, and other sensory data can be used to learn about anddetermine normality and abnormality of business and plant operations toprovide a means of understanding failure modes and give recommendations.

In step 2310, it can be determined if the power system is operating in adeficient state when confronted with a specific contingency. If it is,then in step 2312, a report is generated providing a summary of theoperational stability and reliability of the system. The summary mayinclude general predictions about the total security and stability ofthe system and/or detailed predictions about the performance of eachelement that makes up the UPS controls and/or the electrical system.

Alternatively, if it is determined that the system is not in a deficientstate in step 2310, then it can be determined on step 2308 if furthercontingencies needs to be evaluated. If so, then the process can revertto step 2306 and further contingencies can be evaluated.

The results of the real-time UPS simulations performed can becommunicated in step 2312 via a report, such as a print out or displayof the status. In addition, the information can be reported via agraphical user interface (thick or thin client) that illustrates thevarious components of the system in graphical format. In suchembodiments, the report can simply comprise a graphical indication ofthe security or insecurity of a component, subsystem, or system,including the whole facility. The results can also be forwarded toassociative memory engine 2318, where they can be stored and madeavailable for predictions, pattern/sequence recognition and ability toimagine, e.g., via memory agents or other techniques in step 2320.

The process of FIG. 23 can be applied to a number of needs including butnot limited to predicting the ability of a given UPS control logicarchitecture to maintain electrical system stability due to: motorstarting and motor sequencing, an example is the assessment of adequacyof a power system in emergency start up of auxiliaries; evaluation ofthe protections such as under frequency and under-voltage load sheddingschemes, example of this is allocation of required load shedding for apotential loss of a power generation source; determination of criticalclearing time of circuit breakers to maintain stability; anddetermination of the sequence of protective device operations andinteractions.

FIG. 24 is a diagram illustrating how the UPS Transient StabilitySimulation Engine works in conjunction with the other elements of theanalytics system to make predictions about the operational aspects ofthe UPS controls solution protecting the electrical system, inaccordance with one embodiment. As depicted herein, the UPS transientstability simulation engine 2402 is housed within an analytics server116 and communicatively connected via a network connection 114 with adata acquisition hub 112, a client terminal 128 and a virtual systemmodel database 526. The virtual system model database 526 can beconfigured to store the virtual system model of the electrical powersystem. The virtual system model is constantly updated with real-timedata from the data acquisition hub 112 to effectively account for thenatural aging effects of the hardware that comprise the total electricalpower system, thus, mirroring the real operating conditions of thesystem. This provides a desirable approach to predicting the operationalaspects of a UPS system protecting an electrical power system operatingunder various contingency situations.

The UPS transient stability simulation engine 2402 is configured tostore and process patterns observed from real-time data fed from the hub112 and predicted data output from a real-time virtual system model ofthe electrical system. These patterns can later be used by the UPStransient stability simulation engine 2402 to make real-time predictions(forecasts) about the various operational aspects of the UPS controlssolution and the electrical system.

The data acquisition hub 112 is communicatively connected via dataconnections 110 to a plurality of sensors that are embedded throughoutthe electrical power system 102 being monitored. The data acquisitionhub 112 may be a standalone unit or integrated within the analyticsserver 116 and can be embodied as a piece of hardware, software, or somecombination thereof. In one embodiment, the data connections 110 are“hard wired” physical data connections (e.g., serial, network, etc.).For example, a serial or parallel cable connection between the sensorsand the hub 112. In another embodiment, the data connections 110 arewireless data connections. For example, a radio frequency (RF),BLUETOOTH™, infrared or equivalent connection between the sensor and thehub 112.

Continuing with FIG. 24, the client 128 is typically a conventional“thin-client” or “thick client” computing device that may utilize avariety of network interfaces (e.g., web browser, CITRIX™, WINDOWSTERMINAL SERVICES™, telnet, or other equivalent thin-client terminalapplications, etc.) to access, create, and/or modify the sensors (e.g.,configuration files, etc.), the analytics engine (e.g., configurationfiles, analytics logic, etc.), the calibration parameters (e.g.,configuration files, calibration parameters, etc.), the virtual systemmodeling engine (e.g., configuration files, simulation parameters,etc.), the virtual system model of the system under management (e.g.,virtual system model operating parameters and configuration files), theUPS transient stability simulation engine (e.g., configuration files,calibration parameters, etc.), and the UPS control logic model (e.g.,interface variables, UPS system operating parameters, etc.).Correspondingly, in one embodiment, the data from the various componentsof the UPS controls, electrical system and the real-time predictions(forecasts) about the various operational aspects of the system can bedisplayed on a client 128 display panel for viewing by a systemadministrator or equivalent. In another embodiment, the data may besummarized in a hard copy report 2404.

As discussed above, the UPS transient stability simulation engine 2402can be configured to work in conjunction with a real-time updatedvirtual system model of the electrical system to make predictions(forecasts) about certain operational aspects of a UPS system protectingthe electrical system when it is subjected to a contingency event. Forexample, in one embodiment, the UPS transient stability simulationengine 2402 can be used to make predictions about the operationalreliability of an electrical power system (protected by a UPS controlssub-system) in response to contingency events such as a loss of power tothe system, loss of distribution lines, damage to system infrastructure,changes in weather conditions, etc. Examples of indicators ofoperational reliability include but are not limited to failure rates,repair rates, and required availability of the power system and of thevarious components that make up the system, etc.

In another embodiment, the operational aspect relates to the voltagestability of the electrical system immediately after being subjected toa major disturbance (i.e., contingency event). Generally speaking,voltage instability stems from the attempts by the UPS controls and loaddynamics to restore power consumption, after the disturbance, in amanner that is beyond the capability of the combined UPS system and theelectrical transmission/generation system. Examples of predictedoperational aspects that are indicative of the voltage stability of anelectrical system subjected to a disturbance include the total systempower capacity, available system power capacity and utilized systempower capacity of the electrical system under being subjected to variouscontingencies. Simply, voltage stability is the ability of the UPScontrols and the electrical system to maintain acceptable voltageprofiles while under the influence of the disturbances.

FIG. 25, is an illustration of the interactions between the UPSTransient Stability Simulation Engine and the UPS control logic model,in accordance with one embodiment. As depicted herein, the UPS transientstability simulation engine 2501 is configured to receive standarddynamic model 2502 (i.e., virtual system model) input and real-timeelectrical systems operations data 2503 from sensors interfaced withcomponents that comprise the electrical system.

As discussed above, the user-defined UPS control logic model 2506interacts with the UPS transient stability simulation engine 2501through interface variables 2504. For example, during the operation of auser-defined UPS control logic model 2506, a generator terminal voltageis typically measured and compared with a reference quantity (voltageset point). Based on the specific UPS control logic for the excitationand AVR, the UPS control logic model 2506 can then compute a predictedgenerator field voltage and return that value back to the UPS transientstability simulation engine 2501 for processing during the simulation.

FIG. 26, is a depiction of the various pre-defined UPS control blocks(functions) that can be used to create a user-defined UPS control logicmodel, in accordance with one embodiment. To create a user-defined UPScontrol logic model, a user would simply select one or more controlblocks 2602 then assemble them into the desired UPS control logic model.Each of the control blocks 2602 represents a discrete UPS control logicfunction. Once assembled, the UPS control logic model looks like themodel diagram depicted in FIG. 27.

Table A presents a list of some common pre-defined UPS control blocksused to create a UPS control logic model with. TABLE A Function CommentInput The input can be generator speed, terminal voltage, field voltageOutput The output can be generator field voltage, generator mechanicalpower Connector This is used to “Tap” the output signals to other blockinput Lead (A + Bs), A cannot be zero Lead-Lag (A + Bs)/(C + Ds), A andC cannot be zero Lead-Lag-Limiter Same as above but with the outputlimiter Lag 1/(A + Bs), A cannot be zero Integrator It is important toprovide the initial value of this block if other than zeroDifferentiator The output is the differential of input Constant Use thisblock for defining constants such as load reference set point inreference Time The output of this block will be the same as thesimulation time Gain The gain cannot be zero Limiter Maximum should begreater than minimum Summer1 Use this block to add three inputs signalsSummer2 Use this block to add two input signals Product The output isequal to product of the inputs Division If it is expected that thedenominator may go to zero add small constant to Max Also known as highvalue selector Min Also known as low value selector Sin The input tothis block should be in radians Cos The input to this block should be inradians Sinh Hyperbolic Sinus Acos Inverse Cosine, i.e., Cos⁻¹ CoshHyperbolic Cosine Arc tan Inverse tangent Tan⁻¹ Exponent Exponential ofinput, i.e., e^(x) Logarithm Logarithm Base e Logarithm Logarithm Base10 Logarithm Logarithm Base 10 Absolute The output is equal to theabsolute value of the input signal Int Use to function to convert a realnumber signal to integer value Sqrt {square root over (x² + y²)} SinwtThe output will be a sinusoidal function of time with frequency of wDelay The output will be the same as input with specified delay DbOutput is the same as input with a specified dead band Ramp The outputreach 1 with specified ramp time Logical Switch The output will be equalto first input if the specified decision signal is otherwise, the secondinputs Time Switch The output will be equal to first input if thesimulation time is less the switching time; o

be equal to second inputs

It should be appreciated, however, that the types of pre-defined UPScontrol block functions listed above in Table A are provided here by wayof example only. In practice, the UPS control blocks can model any typeof UPS control logic function as long as the UPS transient stabilitysimulation engine can be used to simulate it.

FIG. 27 is an illustration that depicts the process of building a UPScontrol logic model, in accordance with one embodiment. As depictedherein, from left to right, the input blocks 2702 (these are variablesthat are taken from the electrical power system) are chosen, then, thecontrol block diagram of the controller is built using transfer functionblocks 2704, and finally a specific computed variable is assigned to bethe output blocks 2706.

In one embodiment, a user-defined UPS control logic model is built inaccordance with the following detailed steps. Initially, a control blockdiagram of the UPS control system (normally provided by themanufacturer) to be modeled is obtained by the user. FIGS. 28A and 28Bare sample illustrations of control block diagrams for an excitationsystem and a turbine system, respectively. The user then examines thelist of pre-defined UPS control functions that are supported by the UPStransient stability simulation engine to decide which control functionsare needed to build the UPS control logic model depicted in the controlblock diagram to be modeled. Next, the interface variables thatfacilitate the interactions between the UPS control logic model and theUPS transient stability simulation engine are identified. As discussedabove, examples of UPS interface variables include, but are not limitedto, generator voltage values, generator speed values, automatic voltageregulator (AVR) field voltage variables, governor mechanical powervariables, etc. It should be understood, however, that the interfacevariables discussed above are provided here by way of example only. Inpractice, the interface variables can be any configuration setting forany control element type, as long as the control element can besimulated by the UPS transient stability simulation engine.

The user then proceeds to identify which control block output requestrequires initialization. Typically, the exciter reference, governor loadreference (initial loading) of the turbine, and the initial value of“integrator” blocks require initialization. Once the required UPScontrol functions have been chosen and the interface variablesidentified and classified according to initialization requirement thenthe UPS control logic model can be assembled and created. The newlycreated UPS control logic model can then be added to either the AVR orgovernor library and is ready to be tested by the UPS transientstability simulation engine under various contingency conditions.

In one embodiment, the interface variables of the control system areinitialized in accordance with the following steps and operations.First, the boundary conditions are identified. Examples of boundaryconditions include, but are not limited to, generator terminal voltages,generator field voltages, generator mechanical power, generator speed(frequency), etc. Where applicable, the Laplace symbol in the controlblocks are set to zero. For example, the LEAD-LAG block can be reducedto a block gain of one (i.e., initial output=initial input). Typically,this process works from known boundary conditions inwards to initializeother variables. Once the integrator block (1/s) is reached, the inputis set to zero (this is due to the fact that in steady-state, the inputto an integrator has to be zero in order for the output to be insteady-state). At this point, an attempt can be made to find the outputof the block from the known boundary conditions.

All interface variables are typically presented on a per unit (p.u.)basis on the generator base (e.g., the terminal voltage in p.u.,mechanical power in p.u., etc.). However, the user can still, within thecontrol system, use actual values if necessary. For example, if the AVRcontrol requires that the terminal voltage be in volts, the fieldvoltage can also be computed in terms of volts. This is done by simplyintroducing a gain block right after the terminal voltage with a gainequal to the conversion factor between a p.u. unit and a volt. Thesymbols “+”, “−”, “*”, and “i” represent addition, subtraction,multiplication and division respectively, and should not be used in thename of any output variables or parameters. “(“and”)” can be used togroup an expression for defining the initial conditions. The number of“(” (open parentheses) should match the number of “)” (closedparentheses). Symbols VTO,0, EFD0, PM0, and FREQ0 are reserved names andcan be used to define expressions. These symbols represent the initialconditions (value at time zero) of the generator voltage (in p.u.), thegenerator field voltage (in p.u.), generator mechanical power (in p.u.),and generator speed (p.u.), respectively. These symbols can also be usedto provide the initial values for other output initial conditions. Anyother symbols used in defining an express should be defined asparameters in the control function blocks.

FIG. 29 is an illustration of a closed loop AVR control logic modelbuilt with the pre-defined control logic blocks, in accordance with oneembodiment. As depicted, herein, the voltage 2902 is computed bysimulating the generator response through an open circuit transient timeconstant. However, note that the input block (generator terminalvoltage) and the output block (generator field voltage) are not used inthis model.

The UPS system is designed to provide continuous and clean electricalpower to critical loads within the electrical power system. Also, theUPS system is configured to monitor power conditions affecting thatload. In the event of input power failure, the UPS can be configured tosupply power support the critical load in the electrical system for aperiod up to the specified life of the UPS battery. If the input poweris not restored promptly to the electrical system, back-up power fromthe UPS battery can allow the orderly shutdown of sensitive equipment onthe electrical system that is supported by the UPS.

The UPS can provide two power paths between the source (utility) and thecritical load: a normal power path and a bypass power path. FIG. 30 isan illustration of the power path in a UPS system module during a normaloperation mode, in accordance with one embodiment. As shown in FIG. 30,the power path travels from the AC input 3002 (i.e., utility) to therectifier 3004 and then the inverter 3006, respectively. The rectifier3004 is configured to convert the input 3002 AC power to DC power. DCpower is normally used to charge the UPS battery 3005 and provide powerto the inverter 3006. The inverter 3006 is configured to convert the DCpower to “clean” AC power to supply the critical load (output) 3008. Theconversion and inversion process eliminates any voltage transients orfluctuations existing in the AC input 3002 power before it reaches thecritical load 3008. Typically, source and load side are workingasynchronously. In the event of failure of the UPS system module 3010,power will still be continually supplied to the critical load bydistributing the burden throughout the other UPS system modulesprotecting the electrical system. In the event of a load over-current(spike), the UPS system will switch to a bypass mode withoutinterrupting power to the critical load.

FIG. 31 is an illustration of the power path in a UPS system moduleduring a bypass operation mode, in accordance with one embodiment. Asdepicted herein, the bypass line originates from the AC input 3002(utility) and continues through the CB3 3102 and 52S 3106 bypasscontactors to supply the critical load (output) 3008 with“unconditioned” input power. In one embodiment, the bypass operationoccurs in the event of a load over-current event, with all the UPSmodules 3010 transferring to a bypass mode without any interruptions inpower to the critical load 3008. The internal UPS control logic monitorsthe load on the electrical system and ultimately determines when toswitch from the normal operation mode to the bypass operation mode. Inanother embodiment, the internal static bypass path can be used to routepower to the critical load 3008 while the UPS system module 3010 isde-energized during start-up and before the module 3010 is fullyoperational.

FIG. 33 is an illustration of a UPS control logic diagram thatdemonstrates how the UPS system functions when operating under a bypassoperation mode, in accordance with one embodiment. As shown herein,there are two circuit breakers (STS1 3302 and STS2 3304) that are usedto switch the system between a normal UPS operation mode and a UPSbypass operation mode. During normal operation mode, the STS1 3302breaker operates in a closed state and the STS2 3304 breaker operates inan open state. When the UPS system detects that the system voltage,frequency or current violates the normal operational ranges, the STS13302 breaker will operate in an open state and the STS2 3304 breakerwill operate in a closed state to bypass the input power, away from theUPS rectifier and inverter, to directly power the critical load.

FIG. 34 is a depiction of an input window with sample user-definedsystem conditions triggering the UPS control logic to switch the UPSsystem to a bypass operation mode, in accordance with one embodiment. Asdepicted in the window, a bypass operation would be triggered if thesystem load violates the normal load operational range values for aduration of at least 4 milliseconds (TR 3412). That is, UPS system willswitch to a bypass operation mode if, for a time duration of at least 4milliseconds (TR 3412): 1. the system load has a voltage value that is5% lesser than (VL 3402) or greater than (VH 3404) the normal systemload voltage setting value, 2. the system load is operating at afrequency that is 5% lesser than (FL 3406) or greater than (FU 3408) thenormal system frequency setting value, and/or 3. the system load has acurrent value of greater than 1440 amps (IU 3410). The switch to thebypass operation mode will occur 8 milliseconds after the load conditionviolates any of the normal load operational range values (TD 3414). Thatis, the STS1 breaker opens and the STS2 breaker closes to complete theswitch to a bypass operational mode.

FIG. 35 is a depiction of a UPS simulation results window showing thepower and current flows into the STS1 and STS2 breaker as the UPS systemswitches from a normal operation mode to a bypass operation mode, inaccordance with one embodiment. As shown in this depiction, the activepower flow 3502, reactive power flow 3504 and current flow 3506 throughthe STS1 and STS2 breakers stops for a short period (about 12milliseconds) after the fault (violation of set load conditions) hasbeen detected and the UPS system bypasses the flows directly to thecritical load. Correspondingly, power is also lost for a short period atthe load bus as depicted in FIG. 36. That is, the voltage 3602, voltageangle 3604 and load frequency 3604 values at the load bus momentarilygoes to zero as illustrated in FIG. 36.

FIG. 32 is an illustration of the power path in a UPS system moduleduring a battery power operation mode, in accordance with oneembodiment. As depicted herein, during an AC power input 3002 sourcefailure or interruption, each UPS rectifier 3004 will de-energize andeach UPS battery 3005 will immediately discharge and supply DC power tothe UPS inverter 3006 in order to maintain continuous AC power to thecritical load 3008. This operation will continue until either the UPSbattery 3005 is drained and the inverter 3006 turns off or when theinput power 3002 is restored, after which the rectifier 3004 will againpower the inverter 3006 and the critical load 3008 while simultaneouslyrecharging the UPS battery 3005.

FIG. 37 is a diagram illustrating how the Power System Simulation Engineworks in conjunction with the other elements of the analytics system tomake “what-if” predictions about the health, performance and reliabilityof an electrical system, in accordance with one embodiment. The abilityto determine the health of an electrical power system through a fullysynchronized “blackboard” capability may provide crucial insight intothe availability of the electrical system and its ability to satisfyloading demands under various proposed operational conditions.

Currently, no simulation or “blackboard” solution exists for real-timeanalysis on the health, performance, and reliability of an electricalpower system subjected to various “what-if” scenarios. That is, there isno “what-if” scenario simulator that integrates an electrical networkmodel that can age and synchronize itself in real-time with the actualfacility operating conditions to make predictions about aspects that arereflective of the system's reliability, availability, health andperformance in relation to the life cycle of the system. Withoutoperational condition synchronization or an aging ability, reliabilityindices and “what-if” predictions become of little value as they are nolonger reflective of the actual facility status and may lead to falseconclusions.

There are a number of different electrical system performance aspectsthat can be simulated using a “blackboard” simulation approach thattests various “what if” conditions, including, but not limited to:

Power System Health and Performance

-   -   Examining various “what-if” variations or deviations from expert        power system designs (i.e., the design base).    -   The design base is integrated into a real-time management        environment.

System Reliability and Availability

-   -   Examining changes to system, process and load point reliability        indices under various “what-if” scenarios.    -   Analyzing various potential technological solutions to achieving        reliability centered maintenance.

Power System Capacity levels (total and at each bus)

-   -   Determining total capacity of the electrical system as designed        overall and for each bus under various “what-if” scenarios.    -   Determining how much excess capacity remains or is available        under various “what-if” scenarios.    -   Determining what the present utilized capacity is under various        “what-if” scenarios.

Power System Strength and Resilience

-   -   Predicting dynamic stability across all contingency events        and/or various “what-if” scenarios.    -   Determining protection system stress and withstand status across        all contingency events and/or various “what-if” scenarios.

With the insight gained through this method of visualization andprediction, owners and operators can efficiently manage their businesscritical operations. This allows the use of multiple fully synchronizedsimulation models for performing predictions and “what-if” analysis on apower system within a real-time management environment. That is, this isthe only solution that uses an on-line, real-time system snap shotcaptured by a real-time data acquisition platform to perform thereal-time predictions on the availability, performance, health andreliability of a power network for both the predictions used formanagement of the system and the blackboard predictions used tomanipulate the system and predict system behavior based on proposedoperational changes (e.g., increased loading, facility expansionstrategies, etc.) in a “what if” scenario analysis. Static systemssimply cannot adjust to the many daily changes to the electrical systemthat occur at a facility (motors and pumps may be on or off, on-sitegeneration status may have changed by having diesel generators on-line,utility electrical feed may also change . . . etc.) nor can they agewith the facility to accurately predict the required indices.

The blackboard simulation solution utilizes a variety of methodsincluding AC/DC fast linear network power flow and dynamic simulationsolutions techniques (such as application of trapezoidal algorithms) andsupports:

-   -   Multiple contingency modeling    -   Multiple load levels    -   Automatic or user-selected contingency enumeration    -   Use a variety of remedial actions    -   System and load point reliability indices    -   Sophisticated report generation, color annotation, and text        annotation on the thin client user interface.

As depicted herein FIG. 37, the power system simulation engine 3702 ishoused within an analytics server 116 and communicatively connected viaa network connection 114 with a data acquisition hub 112, a clientterminal 128 and a virtual system model database 526. The virtual systemmodel database 526 can be configured to store the virtual system modelof the electrical power system. The virtual system model is constantlyupdated with real-time data from the data acquisition hub 112 toeffectively account for the natural aging effects of the hardware thatcomprise the total electrical power system, thus, mirroring the realoperating conditions of the system. This provides a desirable approachto predicting the operational aspects of the electrical system operatingunder various “what-if” scenarios (i.e., blackboard virtual systemmodels).

The power system simulation engine 3702 is configured to store andprocess patterns observed from real-time data fed from the hub 112 andpredicted data output from a real-time virtual system model of theelectrical system. These patterns can later be used by the power systemsimulation engine 3702 to make real-time predictions (forecasts) aboutthe operational aspects of the electrical system under variouscustomized “what-if” scenarios.

The data acquisition hub 112 is communicatively connected via dataconnections 110 to a plurality of sensors that are embedded throughoutthe electrical power system 102 being monitored. The data acquisitionhub 112 may be a standalone unit or integrated within the analyticsserver 116 and can be embodied as a piece of hardware, software, or somecombination thereof. In one embodiment, the data connections 110 are“hard wired” physical data connections (e.g., serial, network, etc.).For example, a serial or parallel cable connection between the sensorsand the hub 112. In another embodiment, the data connections 110 arewireless data connections. For example, a radio frequency (RF),BLUETOOTH™, infrared or equivalent connection between the sensor and thehub 112.

Continuing with FIG. 37, the client 128 is typically a conventional“thin-client” or “thick client” computing device that may utilize avariety of network interfaces (e.g., web browser, CITRIX™, WINDOWSTERMINAL SERVICES™, telnet, or other equivalent thin-client terminalapplications, etc.) to access, create, and/or modify the sensors (e.g.,configuration files, etc.), the analytics engine (e.g., configurationfiles, analytics logic, etc.), the calibration parameters (e.g.,configuration files, calibration parameters, etc.), the virtual systemmodeling engine (e.g., configuration files, simulation parameters,etc.), the virtual system model of the system under management (e.g.,virtual system model operating parameters and configuration files),power system simulation engine 3702 (e.g., configuration files,calibration parameters, etc.), and the blackboard “what if” scenarios3704 (e.g., proposed operational changes to load point reliabilityindices, load set points, equipment additions to the power system,implementation of proposed remedial systems, contingency events, etc.).Correspondingly, in one embodiment, the data from the various componentsof the electrical system and the real-time predictions (forecasts) aboutthe various operational aspects of the virtual model system and the“what-if” scenarios (i.e., blackboard virtual system models) can bedisplayed on a client 128 display panel for viewing by a systemadministrator or equivalent. In another embodiment, the data may besummarized in a hard copy report 2404.

As discussed above, the power system simulation engine 3702 can beconfigured to work in conjunction with a real-time updated virtualsystem model of the electrical system to make predictions (forecasts)about certain operational aspects of the electrical system under various“what-if” scenarios (i.e., blackboard virtual system models). These“what-if” scenarios are created by switching the power system simulationengine 3702 into a scenario builder mode (i.e., blackboard virtualsystem model simulation mode) where various parameters of the mostupdated virtual system model of the electrical system can be modified totest various “what-if” scenarios. That is, two models are deployedsimultaneously in the power system simulation engine 3702.

A first logical model (i.e., the virtual system model) that is fullysynchronized (i.e., real-time updated) and used to perform predictionsfor alarm management and facility operations. These predictions arecompared with real-time values to determine health and performance ofthe system and intelligently filter the data stream by analyzing andcomparing in real-time. A second logical model (i.e., modified virtualsystem model or blackboard virtual system model), that is created bymodifying various parameters of the virtual system model (i.e., firstlogical model) to test various “what-if” scenarios. Examples ofparameters that can be modified include, but are not limited to: aselection of electrical system components, system component operationparameters/configurations (e.g., power load set points, electricalsystem/bus load point reliability indices, equipment power capacityratings, etc.), contingency events, remedial systems for correctingproblems with electrical system performance, etc.

Some examples of contingency events include but are not limited to:

-   -   Application/removal of three-phase fault;    -   Application/removal of phase-to-ground fault;    -   Application/removal of phase-phase-ground fault;    -   Application/removal of phase-phase fault;    -   Branch Addition;    -   Branch Tripping;    -   Starting Induction Motor;    -   Stopping Induction Motor;    -   Shunt Tripping;    -   Shunt Addition (Capacitor and/or Induction);    -   Generator Tripping;    -   SVC Tripping;    -   Impact Loading (Load Changing Mechanical Torque on Induction        Machine;    -   With this option it is actually possible to turn an induction        motor to an induction generator);    -   Loss of Utility Power Supply/Generators/UPS/Distribution        Lines/System    -   Infrastructure; and    -   Load Shedding.

The second logical model allows the user to unsynchronize and perform“what-if” analysis and then automatically re-synchronize with the addedability to refresh and reset the parameters of the second logical model(i.e., the modified virtual system model or blackboard virtual systemmodel) to match that of the original virtual system model (i.e., thefirst logical model). This allows the power system facility's operator,owner and/or executive to test an unlimited number of “what-if”scenarios regarding the configuration of the power system and to makedecisions regarding proposed changes to the system with a high degree ofconfidence as opposed to based on “gut feeling.” The test results arenot used to determine the real-time health and performance of thesystem, but rather to make predictions about how certain operationalaspects of the system would/should behave given current conditionsand/or subjected to certain contingency events if the proposed changes(e.g., increase loading on certain buses, shedding loads, equipmentchanges, etc.) to the power system were to be made.

For example, in one embodiment, the power system simulation engine 3702can be used to make predictions about the operational reliability andavailability (an operational aspect) of a proposed configuration of anelectrical power system. Examples of indicators of operationalreliability include but are not limited to failure rates, repair rates,system/process/load point reliability indices, ability of the electricalsystem to maintain a minimum operational safety level, and requiredavailability of the power system and of the various components that makeup the system, etc.

In another embodiment, the operational aspect relates to the powersystem voltage stability (i.e., power system capacity levels) of theproposed configuration of the electrical system. Examples of predictedoperational aspects that are indicative of the voltage stability of anelectrical system include the total system power capacity, availablesystem power capacity and utilized system power capacity of theelectrical system. Simply, voltage stability is the ability of theelectrical system to maintain acceptable voltage profiles while underthe influence of the disturbances.

In still another embodiment, the operational aspect relates to the powersystem strength and resilience of the proposed configuration of theelectrical system. That is, the ability of the proposed electricalsystem to maintain an acceptably high level of power quality (i.e.,maintaining voltage and frequency output within defined tolerancelimits) when subjected to contingency events such as a loss of power tothe system, loss of distribution lines, damage to system infrastructure,changes in weather conditions, etc.

In other words, the blackboard virtual system model (i.e., the secondlogical model) begins as an identical copy of the virtual system model(i.e., the first logical model). However, users can manipulate theblackboard virtual system model parameters (e.g., re-align breakerstatus, loading conditions, etc.) and see the electrical system'sbehavior to such changes, without effecting the virtual system model(i.e., the first logical model) used to manage the facility.

FIG. 38 is a conceptual depiction of the synchronization of the actualphysical world (right side) and virtual world (left side), in accordancewith one embodiment. As depicted, various elements of the actual world3801 is synchronized with the virtual world 3803 in real-time using thepower analytics system.

The actual world 3801 includes components such as the actual physicalfacility component 3810, sensor and monitoring component 3812, and theactual sensor measurements component 3814 (i.e., real-time data output).Within the actual facility component are sub-components such as thepower equipment 3818 and the power system operational processes 3820that are run on the equipment.

The virtual world 3803 includes components such as the virtual systemmodel 3802 of the actual physical facility 3810, simulated/predicteddata output 3804 from the virtual system model 3802, and a graphicalrepresentation 3808 of the virtual system model 3802 of the actualphysical facility 3810. As is clear from this illustration, changes inthe actual world 3801 (e.g., updates to the actual physical facility,measurable real-time changes to the data output from the facility, etc.)are reflected in updates to the virtual world 3803 (e.g., updates to thevirtual system model, simulation parameters, etc.).

FIG. 39 is an illustration of how a blackboard scenario builder can beused to modify various parameters of a virtual system model forsimulating the impact of various “what-if” scenarios on the health,performance and reliability of an electrical system, in accordance withone embodiment. As depicted and building upon the concepts discussedearlier in FIGS. 3 and 38, in the physical world, sensors 202 producereal-time data 302 for the processes 312 and equipment 314 that make upfacility 102. In the virtual world, simulations 304 of the virtualsystem model 206 provide predicted values 306, which are correlated andsynchronized with the real-time data 302. The real-time data can then becompared to the predicted values so that differences 308 can bedetected. The significance of these differences can be used to determinethe health status 310 of the system. The health stats can then becommunicated to the processes 312 and equipment 314, e.g., via alarmsand indicators, as well as to thin client 128, e.g., via web pages 316.

A blackboard user-interface 3908 is used to modify the parameters ofvirtual world (i.e., to create a blackboard virtual facility model 3902)in order to run simulations 3904 of various “what-if” scenarios and makepredictions 3906 about the various operational aspects of the blackboardvirtual facility model 3902. The ability to re-align the simulationmodels in real-time or as needed by the end user so that it mirrors thereal facility operating conditions, coupled with the ability tocalibrate and age the model as the real facility ages provides the mostdesired approach to predicting status and health of the electricalsystem under the various proposed configuration changes (i.e., “what-if”scenarios) while communicating such status through 2D and 3Dvisualization to help operators, owners and executives understand theimpact that the proposed changes have on the health and predictedperformance of their power networks.

FIG. 40 is a flowchart illustrating an example process for simulatinghow “what-if” scenarios impact the health, performance and reliabilityof an electrical system, in accordance with one embodiment. Method 4000begins with operation 4002 where the first virtual system model of theelectrical system under management is updated in response to thereal-time data. This may include, but is not limited to, modifying thesimulated data output from the first virtual system model, adjusting thelogic/processing parameters utilized by the virtual system modelingengine to simulate the operation of the electrical system,adding/subtracting functional elements of the first virtual systemmodel, etc. It should be understood, that any operational parameter ofthe virtual system modeling engine and/or the first virtual system modelmay be modified by the calibration engine as long as the resultingmodifications can be processed and registered by the virtual systemmodeling engine.

Method 4000 moves on to operation 4004 where a parameter of the firstvirtual system model is modified using a scenario builder application tocreate a second virtual system model. Examples of parameters that can bemodified include, but are not limited to: a selection of electricalsystem components, system component operation parameters/configurations(e.g., power load set points, electrical system/bus load pointreliability indices, equipment power capacity ratings, etc.),contingency events, remedial systems for correcting problems withelectrical system performance, etc.

Some examples of contingency events include but are not limited to:

-   -   Application/removal of three-phase fault;    -   Application/removal of phase-to-ground fault;    -   Application/removal of phase-phase-ground fault;    -   Application/removal of phase-phase fault;    -   Branch Addition;    -   Branch Tripping;    -   Starting Induction Motor;    -   Stopping Induction Motor;    -   Shunt Tripping;    -   Shunt Addition (capacitor and/or inductor);    -   Generator Tripping;    -   SVC Tripping;    -   Impact Loading (Load Changing Mechanical Torque on Induction        Machine;    -   With this option it is actually possible to turn an induction        motor to an induction generator);    -   Loss of Utility Power Supply/Generators/UPS/Distribution        Lines/System    -   Infrastructure; and    -   Load Shedding.

The scenario builder application (or blackboard user interface) allowsusers to manipulate the virtual system model parameters (e.g., re-alignbreaker status, loading conditions, etc.) to create a second virtualsystem model (i.e., blackboard virtual system model) and see theelectrical system's behavior to such changes, without effecting thefirst virtual system model (i.e., the first logical model) used tomanage the facility.

Method 4000 continuing on to operation 4006 where electrical systemperformance is simulated using the second virtual system model. Asdiscussed above, the second virtual system model allows the user tounsynchronize and perform “what-if” analysis and then automaticallyre-synchronize with the added ability to refresh and reset theparameters of the second virtual system model (i.e., the modifiedvirtual system model or blackboard virtual system model) to match thatof the original virtual system model (i.e., the first virtual systemmodel). This allows the power system facility's operator, owner and/orexecutive to test an unlimited number of “what-if” scenarios regardingthe configuration of the power system and to make decisions regardingproposed changes to the system with a high degree of confidence asopposed to based on “gut feeling.”

Method 4000 proceeds on to operation 4008 where a report that forecastsan operational aspect of the electrical system is generated. Forexample, in one embodiment, the operation aspect is the reliability andavailability of a proposed configuration (in the second virtual systemmodel) of an electrical power system. Examples of indicators ofoperational reliability include but are not limited to failure rates,repair rates, system/process/load point reliability indices, ability ofthe electrical system to maintain a minimum operational safety level,and required availability of the power system and of the variouscomponents that make up the system, etc.

In another embodiment, the operational aspect relates to the powersystem voltage stability (i.e., power system capacity levels) of theproposed configuration of the electrical system. Examples of predictedoperational aspects that are indicative of the voltage stability of anelectrical system include the total system power capacity, availablesystem power capacity and utilized system power capacity of theelectrical system. Simply, voltage stability is the ability of theelectrical system to maintain acceptable voltage profiles while underthe influence of the disturbances.

In still another embodiment, the operational aspect relates to the powersystem strength and resilience of the proposed configuration of theelectrical system. That is, the ability of the proposed electricalsystem to maintain an acceptably high level of power quality (i.e.,maintaining voltage and frequency output within defined tolerancelimits) when subjected to contingency events such as a loss of power tothe system, loss of distribution lines, damage to system infrastructure,changes in weather conditions, etc.

FIG. 41 is a snapshot of a 2D and 3D visualization of the electricalsystem generated by a blackboard simulation, in accordance with oneembodiment. As depicted, the snapshot of the electrical system helpsoperators, owners and executives understand the impact that the proposedchanges (in the blackboard virtual system model) have on the health andpredicted performance of their power networks. This snapshot can provideinformation such as the proposed electrical system's failure rates,repair rates, system/process/load point reliability indices, ability ofthe electrical system to maintain a minimum operational safety level,and required availability of the power system and of the variouscomponents that make up the system, etc.

The embodiments described herein, can be practiced with other computersystem configurations including hand-held devices, microprocessorsystems, microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers and the like. The embodiments canalso be practiced in distributing computing environments where tasks areperformed by remote processing devices that are linked through anetwork.

It should also be understood that the embodiments described herein canemploy various computer-implemented operations involving data stored incomputer systems. These operations are those requiring physicalmanipulation of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. Further, the manipulations performed are often referred toin terms, such as producing, identifying, determining, or comparing.

Any of the operations that form part of the embodiments described hereinare useful machine operations. The invention also relates to a device oran apparatus for performing these operations. The systems and methodsdescribed herein can be specially constructed for the required purposes,such as the carrier network discussed above, or it may be a generalpurpose computer selectively activated or configured by a computerprogram stored in the computer. In particular, various general purposemachines may be used with computer programs written in accordance withthe teachings herein, or it may be more convenient to construct a morespecialized apparatus to perform the required operations.

Certain embodiments can also be embodied as computer readable code on acomputer readable medium. The computer readable medium is any datastorage device that can store data, which can thereafter be read by acomputer system. Examples of the computer readable medium include harddrives, network attached storage (NAS), read-only memory, random-accessmemory, CD-ROMs, CD-Rs, CD-RWs, magnetic tapes, and other optical andnon-optical data storage devices. The computer readable medium can alsobe distributed over a network coupled computer systems so that thecomputer readable code is stored and executed in a distributed fashion.

Although a few embodiments of the present invention have been describedin detail herein, it should be understood, by those of ordinary skill,that the present invention may be embodied in many other specific formswithout departing from the spirit or scope of the invention. Therefore,the present examples and embodiments are to be considered asillustrative and not restrictive, and the invention is not to be limitedto the details provided therein, but may be modified and practicedwithin the scope of the appended claims.

1. A system for real-time modeling of electrical system performance,comprising: a data acquisition component communicatively connected to asensor configured to acquire real-time data output from the electricalsystem; an analytics server communicatively connected to the dataacquisition component, comprising, a virtual system modeling engineconfigured to generate predicted data output for the electrical systemutilizing a first virtual system model of the electrical system, ananalytics engine configured to monitor the real-time data output and thepredicted data output of the electrical system, the analytics enginefurther configured to initiate a calibration and synchronizationoperation to update the first virtual system model when a differencebetween the real-time data output and the predicted data output exceedsa threshold, and a power system simulation engine configured to storeand process patterns observed from the real-time data output and thepredicted data output, the power system simulation engine furtherconfigured to operate in a scenario builder mode to facilitatemodification of parameters on the first virtual system model to create asecond virtual system model and to forecast an aspect of the electricalsystem operating under the modified parameters of the second virtualsystem model; and a client terminal communicatively connected to thepower system simulation engine, the client terminal configured to allowa system administrator to modify the parameters of the first virtualsystem model when the power system simulation engine is operating in thescenario builder mode and display a report of the forecasted aspects. 2.The system for real-time modeling of electrical system performance, asrecited in claim 1, wherein the power analytics simulation engineincludes, an associative memory layer, a sensory layer, and aneocortical model.
 3. The system for real-time modeling of electricalsystem performance, as recited in claim 1, wherein the modifiedparameters include a selection of electrical system components andcomponent operational parameters.
 4. The system for real-time modelingof electrical system performance, as recited in claim 1, wherein themodified parameters include a selection of contingency events that thevirtual system model is subjected to during the simulation.
 5. Thesystem for real-time modeling of electrical system performance, asrecited in claim 1, wherein the modified parameters include a selectionof remedial systems for correcting problems with electrical systemperformance.
 6. The system for real-time modeling of electrical systemperformance, as recited in claim 1, wherein the modified parametersinclude a selection of electrical system and load point reliabilityindices.
 7. The system for real-time modeling of electrical systemperformance, as recited in claim 1, wherein the modified parametersinclude a selection of power load set points.
 8. The system forreal-time modeling of electrical system performance, as recited in claim1, wherein the aspect is a predicted ability of the electrical system tomaintain an acceptably high level of power quality.
 9. The system forreal-time modeling of electrical system performance, as recited in claim4, wherein the aspect is a predicted ability of the electrical system tomaintain an acceptably high level of power quality when subjected to acontingency event.
 10. The system for real-time modeling of electricalsystem performance, as recited in claim 8, wherein the power qualitylevel is high when the electrical system maintains a voltage andfrequency output within defined tolerance limits.
 11. The system forreal-time modeling of electrical system performance, as recited in claim1, wherein the aspect is the predicted total power system capacity forthe electrical system.
 12. The system for real-time modeling ofelectrical system performance, as recited in claim 1, wherein the aspectis a predicted ability of the electrical system to maintain sufficientactive and reactive power reserves in the electrical system.
 13. Thesystem for real-time modeling of electrical system performance, asrecited in claim 1, wherein the aspect is a predicted ability of theelectrical system to maintain a minimum level of electrical systemreliability and availability.
 14. The system for real-time modeling ofelectrical system performance, as recited in claim 4, wherein the aspectis a predicted ability of the electrical system to maintain a minimumelectrical system operational safety level during the simulatedcontingency event.
 15. The system for real-time modeling of electricalsystem performance, as recited in claim 4, wherein the aspect is apredicted ability of the electrical system to maintain minimumelectrical system operational costs during the simulated contingencyevent.
 16. The system for real-time modeling of electrical systemperformance, as recited in claim 4, wherein the aspect is a predictedability of the electrical system to maintain operational stability inthe electrical system when subjected to the simulated contingency event.17. The system for real-time modeling of electrical system performance,as recited in claim 16, wherein operational stability is a measure ofthe electrical system's ability to maintain stability and recover fromthe contingency event without violating operational constraints of theelectrical system.
 18. A computer implemented method for real-timemodeling of electrical system performance, comprising: updating a firstvirtual system model of the electrical system in response to real-timedata; modifying a parameter of the first virtual system model to createa second virtual system model, using a scenario builder application;simulating electrical system performance using the second virtual systemmodel; and generating a report that forecasts an aspect of theelectrical system.
 19. The computer implemented method for real-timemodeling of electrical system performance, as recited in claim 18,wherein the modified parameter is a selection of one of an electricalsystem component or component operational parameter.
 20. The computerimplemented method for real-time modeling of electrical systemperformance, as recited in claim 18, wherein the modified parameter is aselection of a contingency event that the second virtual system model issubjected to during the simulation.
 21. The computer implemented methodfor real-time modeling of electrical system performance, as recited inclaim 18, wherein the modified parameters is a selection of a remedialsystem for correcting problems with electrical system performance. 22.The computer implemented method for real-time modeling of electricalsystem performance, as recited in claim 18, wherein the modifiedparameter is a selection of one of an electrical system reliabilityindex or load point reliability index.
 23. The computer implementedmethod for real-time modeling of electrical system performance, asrecited in claim 18, wherein the modified parameter is a selection of apower load set point.
 24. The computer implemented method for real-timemodeling of electrical system performance, as recited in claim 18,wherein the aspect is a predicted ability of the electrical system tomaintain an acceptably high level of power quality.
 25. The computerimplemented method for real-time modeling of electrical systemperformance, as recited in claim 18, wherein the aspect is a predictedability of the electrical system to maintain an acceptably high level ofpower quality when subjected to a contingency event.